Re: Sling Scheduler and Quartz Thread Pool Implementation

Digging further - Think we default setup which uses unbounded queue for the threadpool the task would not be subjected to CallerRunsPolicy. So things should work fine Chetan Mehrotra On Fri, Jul 8, 2016 at 3:46 PM, Chetan Mehrotra wrote: > On Fri, Jul 8, 2016 at 3:21

Re: Sling Scheduler and Quartz Thread Pool Implementation

On Fri, Jul 8, 2016 at 3:21 PM, Carsten Ziegeler wrote: > I don't know the answer, but are you experiencing problems in this area? Not directly but I see potential issue. With current approach I think when pool is fully used Quartz would still attempt to runInThread which

Re: Sling Scheduler and Quartz Thread Pool Implementation

I don't know the answer, but are you experiencing problems in this area? Carsten Chetan Mehrotra wrote > Hi, > > Looking at the QuartzThreadPool#blockForAvailableThreads impl [1] > > --- > @Override > public int blockForAvailableThreads() { >return

Sling Scheduler and Quartz Thread Pool Implementation

Hi, Looking at the QuartzThreadPool#blockForAvailableThreads impl [1] --- @Override public int blockForAvailableThreads() { return this.executor.getConfiguration().getMaxPoolSize() - this.executor.getConfiguration().getQueueSize(); } --- Above implementation does not "block" as per