[jboss-user] [jBPM] - How to handle failed processes/states due to server crashes?

Michael Wohlfart do-not-reply at jboss.com
Tue Aug 3 04:52:42 EDT 2010

Michael Wohlfart [http://community.jboss.org/people/mwohlf] replied to the discussion

"How to handle failed processes/states due to server crashes?"

To view the discussion, visit: http://community.jboss.org/message/555586#555586

> Correct me I am wrong: Will jBPM4 pick up the processes waiting for a signal if it (jBPM) is embedded in my application only as a lib rather than installed as a service on JBoss. If thats the case then once my spring-jbpm context gets loaded on application start up, jBPM should pick up all the nodes and wait for a signal. 
that's correct the state of your processes is persisted in the database and preserved between reboots, and that should work weather you use the jBoss Service or not, when you signal jBPM looks up the database for your process instance and wait state...
> theory in devguide doesn't provide much explanation of retry interceptor. I mean how to configure, what inputs it will need and such thing. Do we have any example available for retry-interceptor.
i guess you assume the retry-interceptor is more than it actually is, it's  just a try/catch and checks for StaleStateException, you can configure retries, delay and delay-factor, check the sourcecode I haven't seen it's config options documented somewhere


Reply to this message by going to Community

Start a new discussion in jBPM at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20100803/a5ccd103/attachment.html 

More information about the jboss-user mailing list