[jboss-user] [jBPM] - jBPM timers and persistance

eljan do-not-reply at jboss.com
Fri Mar 15 14:16:43 EDT 2013

eljan [https://community.jboss.org/people/eljan] created the discussion

"jBPM timers and persistance"

To view the discussion, visit: https://community.jboss.org/message/803026#803026


Do I understand correctly that currently there is no way for timers to trigger if the session they are in was not active during their scheduled activation time?

So for example, I have a process with a timer and that timer gets scheduled to activate in 3 minutes.
Suddenly my server crashes. I act quickly and get it running again in 5 minutes.
My persistent jBPM application reloads the session with the timer, but as I understand from trying it out and reading this forum this process is now broken. The timer will never fire, because at the time it was supposed to fire, the session was not active.

This behavior would be really undesired for my application scenario with long lasting persistent processes which might last even several years.
I wouldn't want to throw away such a long process, because of a small server hiccup.

Does timer escalation on a task have the same issue? I haven't tried this out yet.

If this is the case then is there an easy way to implement timer behavior myself while still using jBPM timer node and corresponding BPMN 2.0 element? (for example similar to the way I would register a WorkItemHandler for service tasks)
Otherwise it seems that I would need to implement timer as a service task, which I would like to avoid.

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/20130315/720eeafa/attachment.html 

More information about the jboss-user mailing list