On Fri, Jul 8, 2016 at 3:21 PM, Carsten Ziegeler <[email protected]> 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 with default executor policy of CallerRunsPolicy would lead to that job being run on main Quartz thread. If such a job takes long time it would prevent other job from being scheduled even when pool regains capacity. Chetan Mehrotra
