[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2780) Graceful stop of JobExecutor
[
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<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!
Graceful stop of JobExecutor
----------------------------
Key: JBPM-2780
URL: https://jira.jboss.org/jira/browse/JBPM-2780
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: jBPM 3.2.8
Reporter: Bernd Ruecker
Assignee: Alejandro Guizar
Currently when stopping the JobExecutor it stops all running JobExecutorThreads by
calling "stop()" on them. This interrups the thread.
In a scenario where you want to do a "clean" stop (e.g. shutdown the server),
there should be a mechanism to stop the JobExecutor, but let it finish currently executed
jobs and wait for it.
For the implementation it is not hard, I could provide a patch for it as well. Since a
customer currently needs it, it would be nice to commit it to the next released jbpm 3.2.x
version.
--
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