topic Re: Process suspension and reactivation in activiti 5.9 in Alfresco Archive

Process suspension and reactivation in activiti 5.9

tushard — Thu, 19 Apr 2012 17:59:00 GMT

Hi,Activiti 5.9 now supports suspending and resuming process definition and instances. (Ref: http://www.bpm-guide.de/2012/03/01/activiti-5-9-introduces-more-bpmn-2-0-support/) I wanted to test this functionality, so I constructed following workflow. start –> service_task_1 –> service_task_2

Re: Process suspension and reactivation in activiti 5.9

trademak — Fri, 20 Apr 2012 10:05:22 GMT

Hi,

This sounds like a timing issue.
When you start a new process instance, the async jobs are created immediately and also picked up shortly after that by the job executor.
So when you invoke the suspend action, the jobs are already started and keep running.

Best regards,

Re: Process suspension and reactivation in activiti 5.9

ronald_van_kuij — Fri, 20 Apr 2012 11:11:31 GMT

Yep, would be my idea to… But this is only true for async services and not 'timed jobs' like reminders etc… They are suspended afaik.

Re: Process suspension and reactivation in activiti 5.9

tushard — Mon, 23 Apr 2012 19:26:15 GMT

Thanks Tijs and Ronald.

I have a related question. What happens when an async job is created? Tijs, you said that the async jobs are created immediately and also picked up shortly after that by the job executor. Does this mean that upon starting a process having two service tasks marked async = true, the jobExecutor would create two threads, one for each service task? If true, then is it possible to suspend the execution of the second service task, either using RepositoryService.suspendProcessDefinitionByKey or by any other method?

Best Regards,

Tushar

Re: Process suspension and reactivation in activiti 5.9

trademak — Tue, 24 Apr 2012 09:40:01 GMT

Hi Tushar,

When you have two service tasks marked with async = true, the Activiti Engine will create two jobs in the database to execute them.
When you have just one job executor, this job executor thread will pick up the outstanding jobs and execute them one by one.
So it's a matter of timing if you can suspend the process definition before the second service task is executed.
But maybe you can tell a bit more about the background of your questions. Why do you need suspension?

Best regards,

Re: Process suspension and reactivation in activiti 5.9

tushard — Tue, 24 Apr 2012 16:45:07 GMT

Hi Tijs,

Our processes mainly consists of java service tasks. One of our requirement states that a user should be able to suspend a running process and resume it later. The suspend operation would not affect the currently executing service task, but execution of any subsequent service tasks would be suspended. So, we thought that we can use process suspension and reactivation feature of activiti 5.9. Would you please give us some suggestions?

Regards,

Tushar Deshpande

Re: Process suspension and reactivation in activiti 5.9

ronald_van_kuij — Tue, 24 Apr 2012 19:57:41 GMT

Then don't make then asyc… Or do I miss something?

Re: Process suspension and reactivation in activiti 5.9

yldev — Wed, 03 Oct 2012 17:36:19 GMT

Hi,

We have similar requirements as Tushar's. One of the reasons we made our service tasks async=true is to persist run time state.

It seems runtimeService.suspendProcessInstanceById did put the process instance in suspended state, but the process execution keeps going. We are using Activiti 5.10.

Any suggestions on how to suspend/pause then resume a process instance with async service tasks?

Thanks in advance!
yl

Re: Process suspension and reactivation in activiti 5.9

jbarrez — Thu, 04 Oct 2012 06:56:41 GMT

So you mean that async jobs still are being executed, even if the instance/process definition is suspended?

That does sound like a bug. Please create a jira for it if that's the case.

Re: Process suspension and reactivation in activiti 5.9

ptripathi — Tue, 09 Oct 2012 23:40:32 GMT

jbarrez,
create a JIRA:
http://jira.codehaus.org/browse/ACT-1401

Thanks