[jira] [Comment Edited] (SLING-11025) Sling Eventing should use a dedicated threadpool for scheduled events

["Joerg Hoh (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464636#comment-17464636 ] 

Joerg Hoh edited comment on SLING-11025 at 12/23/21, 6:36 PM:
--------------------------------------------------------------

PR for sling-event: https://github.com/apache/sling-org-apache-sling-event/pull/15 merged


was (Author: joerghoh):
PR for sling-event: https://github.com/apache/sling-org-apache-sling-event/pull/15

> Sling Eventing should use a dedicated threadpool for scheduled events
> ---------------------------------------------------------------------
>
>                 Key: SLING-11025
>                 URL: https://issues.apache.org/jira/browse/SLING-11025
>             Project: Sling
>          Issue Type: Improvement
>          Components: Event
>    Affects Versions: Distributed Event Admin 1.1.4, Event 4.2.24
>            Reporter: Joerg Hoh
>            Assignee: Joerg Hoh
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Eventing and Job handling should not use the default threadpool of the Sling Scheduler, but a dedicated one.
> affected classes:
> * org.apache.sling.event.impl.jobs.queues.QueueManager
> * org.apache.sling.event.dea.impl.DistributedEventReceiver



--
This message was sent by Atlassian Jira
(v8.20.1#820001)