Stuck job instance due to ActivitiOptimisticLockingException
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2014 01:59 AM
Hi all.
I got this problem, (just look like in this jira ticket, please check it http://jira.codehaus.org/browse/ACT-1853 )
And I could describe it like that:
I encountered multiple stuck instances in ACT_RU_JOB where an async-continuation is attempting to proceed to the next step, encountering ActivitiOptimisticLockingException
Summary:
And here is exception when I start Instance
Please help me, how to solve this exception.
I got this problem, (just look like in this jira ticket, please check it http://jira.codehaus.org/browse/ACT-1853 )
And I could describe it like that:
I encountered multiple stuck instances in ACT_RU_JOB where an async-continuation is attempting to proceed to the next step, encountering ActivitiOptimisticLockingException
Summary:
Basically task A routes directly to task BTask A is an asynchronous taskTask B is a user task
And here is exception when I start Instance
ERROR - ExecuteJobsRunnable.handleMultipleJobs(96) | exception during job execution: ProcessInstance[122907] was updated by another transaction concurrentlyorg.activiti.engine.ActivitiOptimisticLockingException: ProcessInstance[122907] was updated by another transaction concurrently
Please help me, how to solve this exception.
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2014 01:40 AM
I had changed logic of service task, the Thread.sleep() is from 5s to 100ms, so there is no exception at all. Is the error related to job's time out?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2014 04:52 AM
Sorry guys, I have figured it out. It caused by I have multiple engines which 2 of them already activated jobs. So I just turn off 1.
