-
1. Re: If my workflow blows up?
ralfoeldi Dec 5, 2005 1:06 PM (in response to pedrosacosta)Hi Pedro(?)
your workflow state will be in the state of the last successful commit(s).
What gets lost are the active threads at the point of the crash, i.e. if some outside event triggered the execution you will have to make sure that these get picked up again.
Two examples:
User Interface: The user will see the 'old' tasks and have to trigger them again.
JMS Messages: put the acceptance of the Message in the same transaction as the changes to the workflow state and the message will get redelivered.
Does that answer your question?
Greetings
Rainer -
2. Re: If my workflow blows up?
aguizar Dec 5, 2005 1:07 PM (in response to pedrosacosta)The jBPM programming model indicates signaling tokens within a transaction. If you do so, your workflow will move from a saved wait state to a new wait state.
If the machine stops, ongoing transactions will not have a chance to commit, and your workflow will remain in the saved state. The application must, however, signal tokens to resume execution. -
3. Re: If my workflow blows up?
pedrosacosta Dec 6, 2005 7:38 AM (in response to pedrosacosta)
JMS Messages: put the acceptance of the Message in the same transaction as the changes to the workflow state and the message will get redelivered.
I don't understand this example, could you explain in detail.
Thanks -
4. Re: If my workflow blows up?
ralfoeldi Dec 6, 2005 8:06 AM (in response to pedrosacosta)Hi Pedro,
have a look at JMS Tutorial "Creating Robust JMS Applications" http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/advanced.html.
JMS Messages are one way of triggering transitions. Timers and user interaction are other common triggers.
Rainer
P.S.: There is no "built-in" JMS capability in jBPM at the moment. I think they're working on something in that direction. Search for asych in this forum.