Stefan Egli created SLING-10441:
-----------------------------------
Summary: make discovery independent from scheduler thread pools
Key: SLING-10441
URL: https://issues.apache.org/jira/browse/SLING-10441
Project: Sling
Issue Type: Task
Components: Discovery
Affects Versions: Discovery Oak 1.2.30, Discovery Base 2.0.8, Discovery
Impl 1.2.12, Discovery Commons 1.0.20
Reporter: Stefan Egli
Assignee: Stefan Egli
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)
