On Fri, Jan 20, 2012 at 08:42:21AM +1100, David Powell wrote: > > We are still having some trouble with this which we have not been able to > diagnose.
Hello David, ouch too bad. > Another issue, which I suspect is related is that a workitem may become > "stuck" as I mentioned above. We can often "re-apply" the expression and > have it resume. However, sometimes after we "reapply", the "_ruote" web > interface will show the expression as "cancelling" and it will just stay in > that state. Once it shows "cancelling" we cannot reapply, nor kill it. > Any suggestions about how to further investigate this problem would be > appreciated. "re-apply" will cancel an expression and its children and once it's done, it will apply the expression again (with the same tree and workitem or with a new tree and/or workitem). So at its heart "re-apply" uses the cancel mechanism. An expression begin re-applied shows as "cancelling" and cannot be further cancelled. Killing should go over and place the expression (and its children) in the "dying" state. Is that related to that participant: On Thu, Dec 15, 2011 at 03:26:28PM -0800, David Powell wrote: > > We have a simple participant that touches a file, waits 20s, then > "rewinds". May I see the code of this participant ? What does the expression/tree you're re-applying look like ? Is the re-applied expression a parent expression to the call to the participant mentioned above ? Cheers, -- John Mettraux - http://lambda.io/processi -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
