topic Re: How do Timer intermediate catching event work? in Alfresco Archive

How do Timer intermediate catching event work?

strae — Thu, 21 Apr 2011 11:32:13 GMT

There are process:<?xml version="1.0" encoding="UTF-8"?><definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:activiti="http://activiti.org/bpmn" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlnsmgdc="http:

Re: How do Timer intermediate catching event work?

jbarrez — Fri, 22 Apr 2011 07:06:22 GMT

When execution arrives at the timer event, it doesnt use your thread for waiting. If we would do that, it woudldnt be good for performance.
So a background threadpool is taking care of executing the rest of the process.

So that explains what you see: the main method executed, but the background thread pool has never the time to kick in.

Re: How do Timer intermediate catching event work?

strae — Fri, 22 Apr 2011 07:32:35 GMT

When execution arrives at the timer event, it doesnt use your thread for waiting. If we would do that, it woudldnt be good for performance.
So a background threadpool is taking care of executing the rest of the process.

So that explains what you see: the main method executed, but the background thread pool has never the time to kick in.

Thanks for the reply, but

Whot do you mean about "background thread pool"? I want to run simple bpmn process that first wait the timeout then execute servicetask. Process must have only one instance and run in single thread. Timer have to be configurated by bpmn. I do not want implement timer in my java code, for exemple in service task.

Re: How do Timer intermediate catching event work?

jbarrez — Fri, 22 Apr 2011 07:49:25 GMT

To be able to run timers, enable the job executor as described in http://activiti.org/userguide/index.html#jobExecutorConfiguration. That takes care of the backrgound thread pool.

My point is: if you run in a simple main() method, your process will always stop before it reaches the end state, because your main() methods stops and kills all associated threads.

Re: How do Timer intermediate catching event work?

sonam_ag — Fri, 09 Oct 2015 10:13:04 GMT

Am starting to explore Activiti and using timer before my next service task.
Had to set activiti:async="true" and set the property <code><property name="jobExecutorActivate" value="true" /> </code> to make my one minute timer to work.

Am using a test class to deploy and run instances. After the first instance is created my program exits. Again after a minute I rerun my code(no new instance needed just deploy), the pending service process from the previous instance gets completed.

Wanted to know how is it working? How is the state managed in Activiti?
Do I need to deploy each time or can I keep my program running until all associated threads are over.
Can the system crash?

Re: How do Timer intermediate catching event work?

jbarrez — Tue, 13 Oct 2015 10:53:02 GMT

"How is the state managed in Activiti?"

The state of the process instance is stored as a tree of 'executions', stored in ACT_RU_EXECUTION table.

The timers are 'jobs' and are stored in the 'ACT_RU_JOB' table.

The system can crash, but we're relying on database transaction to bring us from one stable state to the other. If the system crashed, the transaction will be rolled back and the process instance will be in the previous stable state.

Re: How do Timer intermediate catching event work?

hardiku — Tue, 22 Dec 2015 14:15:34 GMT

I am facing very strange behavior of intermediate and boundary event timers. They are working fine in development environment, where i have inspected startTime,dueDate and endTime, every thing is fine (only one activiti engine against one db).

But in QA environment it behaves weird. It does not wait for specified time duration though dueDate is seems to be correct. It executes almost immediately irrespective of time duration specified. I found very strange endTime for the same. Below is the example of such strange timer execution:

start_time_(act_hi_actinst)=2015-12-22 12:54:53.267
duedate_(act_ru_job)=2015-12-22 12:59:58.67 (5 minutes delay)
end_time_(act_hi_actinst)=2015-12-22 18:24:56.997
duration_(act_hi_actinst)=19803728 (strange, its GMT offset, should be 300000)

I have two activiti engines against one db in QA for LB. I don't understand what's going wrong here ?

Re: How do Timer intermediate catching event work?

vasile_dirla — Wed, 23 Dec 2015 09:04:42 GMT

Hi,
@hardiku, since you have two engines did you check if the clock of these machines (where engines are deployed) are in sync ? (this is the first thing which comes in my mind now)