You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2022/11/05 13:46:00 UTC

[jira] [Assigned] (SLING-10410) Log when a job is scheduled to use the default threadpool

     [ https://issues.apache.org/jira/browse/SLING-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joerg Hoh reassigned SLING-10410:
---------------------------------

    Assignee:     (was: Joerg Hoh)

> Log when a job is scheduled to use the default threadpool
> ---------------------------------------------------------
>
>                 Key: SLING-10410
>                 URL: https://issues.apache.org/jira/browse/SLING-10410
>             Project: Sling
>          Issue Type: New Feature
>          Components: Commons
>    Affects Versions: Commons Scheduler 2.7.12
>            Reporter: Joerg Hoh
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> We came across situations where scheduled jobs were not running at the expected time because the default thread pool was exhausted.
> To improve the resolution the scheduler should be able to log any registration of a scheduled job which is using the default thread pool. This logging should be happening on DEBUG level and include relevant pieces of the stacktrace to ease the identification of the location where it is registered.
>  
> https://github.com/apache/sling-org-apache-sling-commons-scheduler/pull/5



--
This message was sent by Atlassian Jira
(v8.20.10#820010)