continue old activ processes automatically after restarting the jBPM 7 server

[net.han...@gmail.com]

Hi,

is it possible to configure jbpm for continue old active processes automatically after jbpm Server reboot.

[Maciej Swiderski]

not sure what you mean by that?

process instances are driven by signals so you would have to signal it (by for example completing user task) to move forward. How do you expect process engine to know when given process instance should move forward…

Maciej

On 21 Aug 2017, at 09:08, net.han...@gmail.com wrote:

Hi,

is it possible to configure jbpm for continue old active processes automatically after jbpm Server reboot.

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/2251c77d-675b-4a3d-a470-36ee42fde35d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[net.han...@gmail.com]

I have business processes with a long runtime. When one of this business processes are active and in the runtime the jbpm server will be reboot or restart, the last state of this process is saved in the database. After start up the jbpm service the open processes must be recovered to final. In my business processes are only automaticly steps, no user tasks.

I hope you can understand my concern.

thx for your help

Hans

[Maciej Swiderski]

if you’re talking about executing process instance at the time server failed (meaning transaction was not committed) then the process instance will be set back to last wait state. Depending how that instance was triggered it might or might not resume automatically. For instance when it was end user who triggered it then it won’t, when it was a timer or async executor then it should.

Maciej

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/c99d0516-b50d-4392-ac74-45ac81b44569%40googlegroups.com.

[net.han...@gmail.com]

if I understand this correctly, my problem is dependent by the start mode. In the case that my business process is started by user, the interrupted process dosn't start automaticly from the last wait state. But when my business process will be started by a timer or async excecutor the process will be continue at the last known position?

Hans

[Maciej Swiderski]

Hans,

On 22 Aug 2017, at 07:37, net.han...@gmail.com wrote:

if I understand this correctly, my problem is dependent by the start mode. In the case that my business process is started by user, the interrupted process dosn't start automaticly from the last wait state. But when my business process will be started by a timer or async excecutor the process will be continue at the last known position?

that’s indeed the expected behaviour 

Maciej

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/04981518-6414-4c2d-b452-e9dd90b77604%40googlegroups.com.