[SLING-5049] Scheduled tasks should set a meaningful thread name during execution

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Commons Scheduler 2.4.10
• Fix Version/s: Commons Scheduler 2.4.12
• Flags: Patch
• Assignee: Carsten Ziegeler
• Reporter: Georg Henzler
• Created: 21/Sep/15 13:23
• Updated: 14/Dec/15 21:24
• Resolved: 21/Sep/15 15:18

Description

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.