You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (Jira)" <ji...@apache.org> on 2024/12/05 09:50:00 UTC
[jira] [Resolved] (SLING-11662) Endless loop in QuartzSchedulerThread.run() with maxPoolSize == queueSize
[ https://issues.apache.org/jira/browse/SLING-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli resolved SLING-11662.
---------------------------------
Resolution: Fixed
PR https://github.com/apache/sling-org-apache-sling-commons-scheduler/pull/6 merged, marking ticket resolved now
> Endless loop in QuartzSchedulerThread.run() with maxPoolSize == queueSize
> -------------------------------------------------------------------------
>
> Key: SLING-11662
> URL: https://issues.apache.org/jira/browse/SLING-11662
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Scheduler 2.7.12
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When configuring the ThreadPool with maxPoolSize == queueSize and endless loop (can) happen(s) in QuartzSchedulerThread.run() which manifests as follows:
> {noformat}
> "MyPool_QuartzSchedulerThread" #123 prio=5 os_prio=0 cpu=5123456.78ms elapsed=5163.45s tid=0x000012345678ff00 nid=0x1234 runnable [0x000087654321ff00]
> java.lang.Thread.State: RUNNABLE
> at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:413)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)