topic Re: Flushing activiti DB updates on Demand in Alfresco Archive

Flushing activiti DB updates on Demand

jorell — Thu, 20 Feb 2014 03:27:39 GMT

I am facing a case where it seems that when I start process and immediately complete the first task (from outside the delegate) the execution for that process hasn;t yet been persisted to the DB. I am unable to fetch the execution by id. My first service task is a delegate which does some work and t

Re: Flushing activiti DB updates on Demand

martin_grofcik — Thu, 20 Feb 2014 07:17:29 GMT

Hi Jorell,

Is there a way for force activiti to flush its cache after a operation like starting a new process?

Try to use async executions. http://www.activiti.org/userguide/#asyncContinuations

immediately complete the first task (from outside the delegate) the execution for that process hasn;t yet been persisted to the DB. I am unable to fetch the execution by id.

Would it be possible to create jUnit test?

Regards
Martin

Re: Flushing activiti DB updates on Demand

jwood — Fri, 21 Feb 2014 18:01:45 GMT

Hi, I just faced the same problem. The first step in my process is a java service which invoked a method via an EL expression. Any attempt to set a variable in that method fails because the process cannot be found. The async suggestion doesnt work for me as I want to immediatly return from the process create knowing where the flow has got to.

I have a work around by putting a Receive Task immediatly after creation and signalling it straight after returning from the startProcessInstanceByKey call. This seems to ensure that the execution is written to the DB.

Is there any way of avoiding this extra step?

Re: Flushing activiti DB updates on Demand

jbarrez — Tue, 25 Feb 2014 09:22:02 GMT

Another solution could be to put a little queue thing in front of that logic, that keeps the message until the process has reached a persistent state.