Discussion:
[jboss-user] [jBPM] - jBPM timers and persistance
eljan
2013-03-15 18:16:43 UTC
Permalink
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

--------------------------------------------------------------
Hi

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
[https://community.jboss.org/message/803026#803026]

Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2034]
Amin Mohammed-Coleman
2013-03-16 09:53:50 UTC
Permalink
Amin Mohammed-Coleman [https://community.jboss.org/people/amin-mc] created the discussion

"Re: jBPM timers and persistance"

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

--------------------------------------------------------------
I find the way timers have been implemented in jBPM 5 very confusing.  It seems as though you need to have a statefulknowledgession active in order to have timers fire.  Why?  Why isn't the implementation of timers and the session kept seperate?  Why can't you have a component that registers the process with the timer node and that component create a session and fires the timer?  Other workflow engines have this sort implementation.  This has been a major issue with implementing jBPM 5.

I don't seem to find any sensible answer to this problem and I expect I won't actually get one.

Rant over.
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/803078#803078]

Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2034]
Loading...