[
https://issues.apache.org/jira/browse/SLING-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365109#comment-14365109
]
Carsten Ziegeler commented on SLING-4481:
-----------------------------------------
I finished the first implementation, the retry handling for ordered queues is
now done by blocking the cache for the retry delay.
I also added additional synchronization for closing the queue and starting a
new job and fixed the canBeClosed method. In the old implementation a queue
might have been closed while it just started to process a new job, which then
resulted in the job being processed twice
> Reduce the number of controller threads for queue
> -------------------------------------------------
>
> Key: SLING-4481
> URL: https://issues.apache.org/jira/browse/SLING-4481
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Event 3.5.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
>
> Right now each queue is using a controller thread which is not taken from a
> pool. WIth a lot of queues this results in a lot of threads - although a
> queue is only started if there is a job for that queue, this still can be a
> significant number.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
