topic Re: Asynchronous / Long Running Activities in Alfresco Archive

Asynchronous / Long Running Activities

dstone_dalet_co — Thu, 12 Mar 2015 17:29:35 GMT

Hi,We are developing a product which uses the Activiti Engine (5.17). We have implemented a number of activities that execute long lived jobs within our system. The prototype versions of these activities were implemented using a script or JavaDelegate based task which submits the job and blocks un

Re: Asynchronous / Long Running Activities

jbarrez — Tue, 17 Mar 2015 09:19:59 GMT

Option is what I prefer, as it keeps database transaction not open when not needed. Your second option is actually the same, but with a step that does both in one go. I like it too 😉

The only thing you must be careful of is that, if your external system is REALLY fast, it will try to signal quicker than that Activiti has continued the process. So you do have to build in a query + wait mechanism.

Re: Asynchronous / Long Running Activities

dstone_dalet_co — Tue, 17 Mar 2015 09:38:11 GMT

Thank you for the reply. It sounds like both options are OK but can I just clarify a few points:
1. Did you say you prefer option 1?
2. I thought both options didn't keep the DB transaction open between the start / execute and signal. Is that not the case? I think in a previous thread it was hinted that option 2 didn't keep the DB open (see http://forums.activiti.org/content/java-service-task-passivate-wout-receive-task);
Thanks for warning me about the fast signal issue.
Many thanks, Dan

Re: Asynchronous / Long Running Activities

jbarrez — Tue, 24 Mar 2015 12:32:16 GMT

1 .Yes, my personal preference is 1. But that is mere taste.
2. Correct, which is what I said. Im just pointing out why it's a good idea.

Re: Asynchronous / Long Running Activities

dstone_dalet_co — Wed, 25 Mar 2015 12:26:59 GMT

Thank you for helping and reassuring me that either option is possible.

Re: Asynchronous / Long Running Activities

boekhold — Thu, 26 Mar 2015 08:46:13 GMT

Joram, sorry if I'm asking a stupid question, but what kind of "query" would you need to do to ensure the task is already in the correct state in which it can receive the signal?