[jboss-user] [jBPM] - jBPM 4.4 How can I activate the 'inactive-concurrent-root'
Kevin Moodley
do-not-reply at jboss.com
Tue Aug 3 01:06:38 EDT 2010
Kevin Moodley [http://community.jboss.org/people/kevinmoodley] created the discussion
"jBPM 4.4 How can I activate the 'inactive-concurrent-root'"
To view the discussion, visit: http://community.jboss.org/message/555543#555543
--------------------------------------------------------------
How can I make the inactive-concurrent-root the active execution?
This is a variation of my earlier question about how to deal with forks and joins when or more of the forks transistions to an error state and the join is therefore never reached.
When the process enters the fork, the state of the root execution is set to 'inactive-concurrent-root'. It only becomes active again after the join. If the join is never reached, (because one of the legs of the fork transitioned to error), the root execution never becomes active again.
Is there a way to force the inactive-concurrent-root to become the active execution?
Or is there a way to force the process to get to the join even if there was an error on one of the nodes leaving the fork?
Thanks
Kevin
http://community.jboss.org/servlet/JiveServlet/showImage/4462/Concurrency.png http://community.jboss.org/servlet/JiveServlet/downloadImage/4462/450-306/Concurrency.png
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/555543#555543]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2034]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20100803/2680e828/attachment.html
More information about the jboss-user
mailing list