[SLING-11585] Invalid configuration for the sling-event thread pool factory

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Starter 13
• Assignee: Eric Norman
• Reporter: Eric Norman
• Created: 16/Sep/22 22:24
• Updated: 17/Sep/22 00:08
• Resolved: 17/Sep/22 00:08

Description

In the starter event.json, the sling-event thread pool factory has an invalid configuration that results in an IllegalArgumentException getting thrown at runtime.  This causes all the scheduled jobs to not get triggered.

Specifically, the maxPoolSize is smaller than the minPoolSize:

 

            "maxPoolSize:Integer":"1",
            "minPoolSize:Integer":"5"

 

The illegal config causes a few exceptions with stack traces like this:

java.lang.IllegalArgumentException
    at java.base/java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1293)
    at org.apache.sling.commons.threads.impl.DefaultThreadPool.<init>(DefaultThreadPool.java:160)
    at org.apache.sling.commons.threads.impl.DefaultThreadPoolManager$Entry.incUsage(DefaultThreadPoolManager.java:371)
    at org.apache.sling.commons.threads.impl.DefaultThreadPoolManager.get(DefaultThreadPoolManager.java:143)
    at org.apache.sling.commons.scheduler.impl.SchedulerProxy.<init>(SchedulerProxy.java:65)
    at org.apache.sling.commons.scheduler.impl.QuartzScheduler.scheduleJob(QuartzScheduler.java:588)
    at org.apache.sling.commons.scheduler.impl.QuartzScheduler.schedule(QuartzScheduler.java:526)
    at org.apache.sling.commons.scheduler.impl.SchedulerServiceFactory.schedule(SchedulerServiceFactory.java:63)

 

Issue Links

• links to: sling-starter - Pull Request #75