topic Re: Imtermediate timer catching event is not running in Alfresco Archive

Imtermediate timer catching event is not running

minhquankq — Tue, 14 Jun 2016 04:43:22 GMT

I have a model below:[img]http://s31.postimg.org/tcod2vph7/Selection_001.png[/img]My expectation is recalling the api if has exception after 30s, when success, will be run as normal.But the process is not continue at Imtermediate timer catching event, It's delay forever.Anyone has ideas?

Re: Imtermediate timer catching event is not running

martin_grofcik — Tue, 14 Jun 2016 06:38:16 GMT

Hi,

Do you have job executor enabled in the process engine config?
Can you reproduce the issue in the jUnit test?
https://forums.activiti.org/content/sticky-how-write-unit-test

Regards
Martin

Re: Imtermediate timer catching event is not running

minhquankq — Tue, 14 Jun 2016 10:13:31 GMT

Hi,

Thank for your responding, I have resolve this issue when upgrade activiti to version 5.20.0 (issue occur with version 5.19.0).

But it's seem work around, I research and found Asynchronous Continuations, but still didn't work.

Regards,

Re: Imtermediate timer catching event is not running

jbarrez — Mon, 20 Jun 2016 12:58:31 GMT

As Martin asked, did you enable the job executor?
Can you post your engine config?

Re: Imtermediate timer catching event is not running

minhquankq — Wed, 22 Jun 2016 06:45:23 GMT

Here is my engine.properties file

<code>
# demo data properties
create.demo.users=true
create.demo.definitions=false
create.demo.models=false
create.demo.reports=false

# engine properties
engine.schema.update=true
engine.activate.jobexecutor=true
engine.asyncexecutor.enabled=true
engine.asyncexecutor.activate=true
engine.history.level=full

# email properties
#engine.email.enabled=true
#engine.email.host=localhost
#engine.email.port=1025
</code>

As my comment above, I have resolved this issue by upgrade to 5.20.0, I just want to confirm that error occurs on 5.19.0

Re: Imtermediate timer catching event is not running

jbarrez — Wed, 22 Jun 2016 08:31:56 GMT

No, it shouldn't… it should be the same. But glad it works for you now on 5.20.