Imtermediate timer catching event is not running

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-14-2016 12:43 AM
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?
[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?
Labels:
- Labels:
-
Archive
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-14-2016 02:38 AM
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
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

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-14-2016 06:13 AM
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,
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,
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-20-2016 08:58 AM
As Martin asked, did you enable the job executor?
Can you post your engine config?
Can you post your engine config?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-22-2016 02:45 AM
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
<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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-22-2016 04:31 AM
No, it shouldn't… it should be the same. But glad it works for you now on 5.20.
