[ https://jira.jboss.org/jira/browse/JBPM-2780?page=com.atlassian.jira.plug... ] Alejandro Guizar edited comment on JBPM-2780 at 2/2/10 8:33 PM: ---------------------------------------------------------------- This description is not accurate. JobExecutor stops JobExecutorThreads by invoking the deactivate() method. deactivate() follows the suggestions for stopping threads that wait for long periods outlined in http://java.sun.com/j2se/1.4.2/docs/guide/misc/threadPrimitiveDeprecation... Thread.interrupt() throws an InterruptedException to the target thread, but only if the thread is blocked in an invocation of Object.wait() or Thread.sleep() among other related methods. Otherwise, the interrupt status is set and the thread keeps running. If a JobExecutorThread is executing a job at the time of deactivation, the job runs till finished. Only then the JobExecutorThread checks its isActive flag and ceases execution. was (Author: alex.guizar(a)jboss.com): This description is not accurate. JobExecutor stops JobExecutorThreads by invoking the deactivate() method. deactivate() follows the suggestions for stopping threads that wait for long periods outlined in http://java.sun.com/j2se/1.4.2/docs/guide/misc/threadPrimitiveDeprecation... Thread::interrupt() throws an InterruptedException to the target thread, but only if the thread is blocked in a call to Object.wait or Thread.sleep among other blocking methods. Otherwise, the interrupt status is set and the thread keeps running. Blocking methods are designed to throw an InterruptedException if the calling thread has its interrupt status set. If a JobExecutorThread is executing a job at the time of deactivation, the job runs till finished. Only then the JobExecutorThread checks its isActive flag and ceases execution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2780?page=com.atlassian.jira.plug... ] Bernd Ruecker commented on JBPM-2780: ------------------------------------- Okay, the testcase did the following in the job to simulate waiting: <node name="node1"> <event type="node-enter"> <script> for (int j=0; j&lt;10; j++) { System.out.println(String.format("test-par %d", new Object[]{j})); try { Thread.sleep(1000); } catch (Exception e) {} } </script> </event> <transition to="end"></transition> </node> So the Thread.sleep in the test case caused the worng behaviour after what you wrote. Again: Thanks a lot for looking into it! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2780?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-2780: ----------------------------------- Remaining Estimate: 0 minutes Original Estimate: 0 minutes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira