[jira] [Created] (SLING-5049) Scheduled tasks should set a meaningful thread name during execution

["Georg Henzler (JIRA)" <ji...@apache.org>]

Georg Henzler created SLING-5049:
------------------------------------

             Summary: Scheduled tasks should set a meaningful thread name during execution
                 Key: SLING-5049
                 URL: https://issues.apache.org/jira/browse/SLING-5049
             Project: Sling
          Issue Type: Improvement
    Affects Versions: Commons Scheduler 2.4.10
            Reporter: Georg Henzler


It would be useful for log file analysis purposes to set a meaningful thread name during the execution of scheduled tasks (https://sling.apache.org/documentation/bundles/scheduler-service-commons-scheduler.html). Both Sling requests and jobs do this already: Requests set Method + URL, Jobs set the name to pool id + queue name + topic. For scheduled tasks I would propose to reuse "QuartzJobScheduler.JobName" that is already used internally (and is derived by OSGi service property "scheduler.name"). This can fairly easily be achieved by a few lines of code in QuartzJobExecutor, see attached patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)