topic Re: Boundary timer event not firing (jobExecutorActivate=true) in Alfresco Archive

Boundary timer event not firing (jobExecutorActivate=true)

gavnunns — Tue, 28 Jan 2014 16:05:59 GMT

Hi I'm having a problem with a boundary timer event not firing. I realize the typical issue for this is <property name="jobExecutorActivate" value="true"/> has not been set to true. That is not the issue here.Below is a snipit of code from my bpmn file. The flow arrives at the user task and

Re: Boundary timer event not firing (jobExecutorActivate=true)

gavnunns — Tue, 28 Jan 2014 16:08:40 GMT

Re: Boundary timer event not firing (jobExecutorActivate=true)

martin_grofcik — Wed, 29 Jan 2014 07:46:24 GMT

Hi Gavin,

I did not find anything wrong there. Advice: Try create jUnit test (you can follow this template:http://forums.activiti.org/content/sticky-how-write-unit-test). Debug it and find rws in ACT_RU_JOB table it could help you to understand and find the problem.

Regards
Martin

Re: Boundary timer event not firing (jobExecutorActivate=true)

gavnunns — Wed, 29 Jan 2014 14:27:22 GMT

Well I'm still baffled, I wrote a unit test and stepped through with debug, it is just not triggering the boundary timer event. I even created a small test flow and the same thing occurred, then I tried placing the boundary event on a sub-process and again, nothing triggered.

What did fix it was upgrading from 5.12 -> 5.14.

Re: Boundary timer event not firing (jobExecutorActivate=true)

martin_grofcik — Thu, 30 Jan 2014 07:37:09 GMT

Hi Gavin,

There is jUnit test testing boundary events on user task in activiti sources. e.g.
org.activiti.engine.test.bpmn.event.timer.BoundaryTimerEventTest#testMultipleTimersOnUserTask
I am pretty sure that the same test is in 5.12. You can try to find it and run it. - May be it helps.

Regards
Martin

Re: Boundary timer event not firing (jobExecutorActivate=true)

gavnunns — Thu, 30 Jan 2014 19:33:04 GMT

Solved - I got the unit tests working but I was still being baffled when the same bpmn was being run from my activiti engine.

Then it dawned on me…. I had two Activiti Engines running and pointing at the same database, a stand alone one and Activiti explorer both with jobExecutorActivate = true, however Activti explorer did not have the correct class path so when it consumed the timed event a error would be thrown and lost in the tomcat logs (which I was not paying any attention too). This also explains why I was getting multiple emails….

It all makes sense now Well at least it forced me to upgrade me to the latest version of Activiti running in all my projects

I'll put this one down to user error