Re: Re: Re: super-kill a process
Dmitry Shulga <[email protected]> Thu, 5 Nov 2009 13:59:19 -0800
| Newsgroups | gmane.comp.java.enhydra.shark |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1257458384-8018-143 Content-Type: multipart/alternative; boundary=000e0cdf974403a1f60477a6d8b7 --000e0cdf974403a1f60477a6d8b7 Content-Type: text/plain; charset=UTF-8 I know exactly why you are asking because I had the same problem. I wanted to terminate the process abruptly if some sort of exceptional case occurs. You may try to use a tool activity that will execute this command as I was advice before but it is not clear how engine will react to that suicide action. I had to abort the process externally. On Thu, Nov 5, 2009 at 1:05 PM, Vojtech Huser <[email protected]>wrote: > OK. That is a possibility. > *How and where would you call this process.abort ?* - in en external > applications which accesses the engine via an API ? (We could do that.But > prefer a different solution. > > Ideally we would do it within the process definition (in the XPDL) - "from > within the process"). > Something like "super-end node" in the XPDL. > > I am not sure if the engine would like a a JavaClassToolAgent which calls > process.abort (Activity tries to kill the Parent Process) ? Would it work > or crash the engine? > > Vojtech > > > > > On Thu, Nov 5, 2009 at 12:04 PM, Dmitry Shulga <[email protected]>wrote: > >> How about process.abort? >> >> On Thu, Nov 5, 2009 at 9:50 AM, Vojtech Huser <[email protected]>wrote: >> >>> Hi, >>> >>> we have a problem and would like some thoughts from others. >>> >>> Shark does in most cases "explicit termination" of a whole process when >>> the 'end node' is reached. (one of the workflow patterns). >>> >>> >>> Most of our activities have automatic start and end but few (which listen >>> for external events) have manual start. >>> We found out that if a process reaches end node and there are some manual >>> activities pending, the process is not terminated (when some end node is >>> reached). >>> >>> *Q:Is there a way to "super-kill" a process (from within). (despite any >>> open activities) (something like clicking the terminate button in the admin >>> client)?.* >>> >>> Vojtech >>> >>> >>> -- >>> You receive this message as a subscriber of the [email protected] mailing >>> list. >>> To unsubscribe: mailto:[email protected] >>> For general help: mailto:[email protected]?subject=help >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> >> >> >> -- >> You receive this message as a subscriber of the [email protected] mailing >> list. >> To unsubscribe: mailto:[email protected] >> For general help: mailto:[email protected]?subject=help >> OW2 mailing lists service home page: http://www.ow2.org/wws >> >> > > > -- > You receive this message as a subscriber of the [email protected] mailing > list. > To unsubscribe: mailto:[email protected] > For general help: mailto:[email protected]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > --000e0cdf974403a1f60477a6d8b7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I know=C2=A0exactly=C2=A0why you are asking because I had the same problem.= I wanted to terminate the process abruptly if some sort of exceptional cas= e occurs. You may try to use a tool activity that will execute this command= =C2=A0as I was advice before but=C2=A0it is not clear how engine will react= to that suicide action. I had to abort the process externally.=C2=A0<br> <br><div class=3D"gmail_quote">On Thu, Nov 5, 2009 at 1:05 PM, Vojtech Huse= r <span dir=3D"ltr"><<a href=3D"mailto:[email protected]">huser.vo= [email protected]</a>></span> wrote:<br><blockquote class=3D"gmail_quote" = style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> OK. That is a possibility.<br><b>How and where would you call this process.= abort ?</b> - in en external applications which accesses the engine via an = API ?=C2=A0 (We could do that.But prefer a different solution.<br><br>Ideal= ly we would do it within the process definition (in the XPDL) - "from = within the process").<br> Something like "super-end node" in the XPDL.<br><br>I am not sure if the engine would like a a JavaClassToolAgent which calls process.abort=C2=A0 (Activity tries to kill the Parent Process) ? Would it work or crash the engine?<br><font color=3D"#888888"> <br>Vojtech<br><br><br><br></font><br><div class=3D"gmail_quote">On Thu, No= v 5, 2009 at 12:04 PM, Dmitry Shulga <span dir=3D"ltr"><<a href=3D"mailt= o:[email protected]" target=3D"_blank">[email protected]</a>>= ;</span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"border-left:1px solid rgb(204, 2= 04, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">How about process.abort= ?<br><br><div class=3D"gmail_quote"><div><div></div><div>On Thu, Nov 5, 200= 9 at 9:50 AM, Vojtech Huser <span dir=3D"ltr"><<a href=3D"mailto:huser.v= [email protected]" target=3D"_blank">[email protected]</a>></span> = wrote:<br> </div></div><blockquote class=3D"gmail_quote" style=3D"border-left:1px soli= d rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex"><div><div><= /div><div> Hi,<br><br>we have a problem and would like some thoughts from others.<br><= br>Shark does in most cases "explicit termination" of a whole pro= cess when the 'end node' is reached. (one of the workflow patterns)= .<br> <br><br>Most of our activities have automatic start and end but few (which = listen for external events) have manual start.<br>We found out that if a pr= ocess reaches end node and there are some manual activities pending, the pr= ocess is not terminated (when some end node is reached).<br> <br><b>Q:Is there a way to "super-kill" a process (from within). = (despite any open activities) (something like clicking the terminate button= in the admin client)?.</b><br><font color=3D"#888888"><br>Vojtech<br> </font><br><br></div></div> --<br> You receive this message as a subscriber of the <a href=3D"mailto:shark@ow2= .org" target=3D"_blank">[email protected]</a> mailing list.<br> To unsubscribe: mailto:<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a><br> For general help: mailto:<a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a>?subject=3Dhelp<br> OW2 mailing lists service home page: <a href=3D"http://www.ow2.org/wws" tar= get=3D"_blank">http://www.ow2.org/wws</a><br> <br></blockquote></div><br> <br><br> --<br> You receive this message as a subscriber of the <a href=3D"mailto:shark@ow2= .org" target=3D"_blank">[email protected]</a> mailing list.<br> To unsubscribe: mailto:<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a><br> For general help: mailto:<a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a>?subject=3Dhelp<br> OW2 mailing lists service home page: <a href=3D"http://www.ow2.org/wws" tar= get=3D"_blank">http://www.ow2.org/wws</a><br> <br></blockquote></div><br> <br><br> --<br> You receive this message as a subscriber of the <a href=3D"mailto:shark@ow2= .org">[email protected]</a> mailing list.<br> To unsubscribe: mailto:<a href=3D"mailto:[email protected]">shark-u= [email protected]</a><br> For general help: mailto:<a href=3D"mailto:[email protected]">[email protected]</a>= ?subject=3Dhelp<br> OW2 mailing lists service home page: <a href=3D"http://www.ow2.org/wws" tar= get=3D"_blank">http://www.ow2.org/wws</a><br> <br></blockquote></div><br> --000e0cdf974403a1f60477a6d8b7-- ------------=_1257458384-8018-143 Content-Type: text/plain; charset="UTF-8"; name="message-footer.txt" Content-Disposition: inline; filename="message-footer.txt" Content-Transfer-Encoding: quoted-printable -- You receive this message as a subscriber of the [email protected] mailing lis= t. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=3Dhelp OW2 mailing lists service home page: http://www.ow2.org/wws ------------=_1257458384-8018-143--