From jira-events at lists.jboss.org Wed Feb  3 13:08:19 2010
Content-Type: multipart/mixed; boundary="===============0091065437421506013=="
MIME-Version: 1.0
From: Bernd Ruecker (JIRA) <jira-events at lists.jboss.org>
To: jbpm-issues at lists.jboss.org
Subject: [jbpm-issues] [JBoss JIRA] Commented: (JBPM-2780) Graceful stop of
 JobExecutor
Date: Wed, 03 Feb 2010 13:08:19 -0500
Message-ID: <1538062095.1265220499540.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
In-Reply-To: 1688189692.1265126839654.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com

--===============0091065437421506013==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


    [ https://jira.jboss.org/jira/browse/JBPM-2780?page=3Dcom.atlassian.jir=
a.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12510190=
#action_12510190 ] =


Bernd Ruecker commented on JBPM-2780:
-------------------------------------

Okay, the testcase did the following in the job to simulate waiting:

    <node name=3D"node1">
        <event type=3D"node-enter">
            <script>
            for (int j=3D0; 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=3D"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 JobExecutorT=
hreads by calling "stop()" on them. This interrups the thread.
> In a scenario where you want to do a "clean" stop (e.g. shutdown the serv=
er), 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: htt=
ps://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       =20

--===============0091065437421506013==--