[
https://issues.apache.org/jira/browse/SLING-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh updated SLING-10410:
------------------------------
Description:
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
was:
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.
> 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: 10m
> 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.3.4#803005)
