[ https://issues.apache.org/jira/browse/SLING-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli updated SLING-10441: -------------------------------- Fix Version/s: Discovery Oak 1.2.34 Discovery Base 2.0.10 Discovery Commons 1.0.24 > use dedicated scheduler thread pool for discovery > ------------------------------------------------- > > Key: SLING-10441 > URL: https://issues.apache.org/jira/browse/SLING-10441 > Project: Sling > Issue Type: Task > Components: Discovery > Affects Versions: Discovery Commons 1.0.20, Discovery Impl 1.2.12, > Discovery Base 2.0.8, Discovery Oak 1.2.30 > Reporter: Stefan Egli > Assignee: Stefan Egli > Priority: Major > Fix For: Discovery Commons 1.0.24, Discovery Base 2.0.10, > Discovery Oak 1.2.34 > > Time Spent: 1h > Remaining Estimate: 0h > > Currently discovery uses the commons.scheduler for a few but mission critical > cases. Since the commons.scheduler doesn't guarantee timely execution - eg > when the corresponding thread pool is full - discovery should become > independent of commons.scheduler. > The easiest solution is to spawn {{new Thread}} in those few cases. This > shouldn't be problematic since these activities are not happening on a high > frequency and are only short-lived. -- This message was sent by Atlassian Jira (v8.3.4#803005)