Description of problem: due to bug introduced by fixing https://bugzilla.redhat.com/show_bug.cgi?id=1036761 the ThreadPoolSchedulerService does not properly shutdown its thread pool causing threads to be left after it RuntimeManager is closed. Version-Release number of selected component (if applicable): How reproducible: Create RuntimeManager with default settings (ThreadPoolSchedulerService with pool size set to 3) then: - execute process with a timer. - examine number of active threads - close RuntimeManager - examine number of active threads last active thread count should not have threads of the scheduler service Steps to Reproduce: 1. 2. 3. Actual results: threads from the scheduler service are still active Expected results: threads from scheduler service should not be present Additional info:
Thanks Maciej for reporting this.
fixed on master, waiting for acks to back port jbpm master: https://github.com/droolsjbpm/jbpm/commit/f1d7f2c315535521bd4da980d303877a114264b9
backported to 6.0.x: https://github.com/droolsjbpm/jbpm/commit/20b457619d4230ace2d3fc47db8033b44fbb4ef2
(6.0.0.GA.x): https://github.com/droolsjbpm/jbpm/commit/8436658 Cherry-picked into 6.0.0.CR2.
Verified in BPMS 6 CR2.