topic Re: ActivitiOptimisticLockingException on even the simplest process in Alfresco Archive

ActivitiOptimisticLockingException on even the simplest process

jbrazil5 — Thu, 05 Dec 2013 19:24:19 GMT

Activiti Version : 5.13Database : MySQLHello Activiti Team!I am still learning about Activiti so sorry if this is a dumb question…I am trying to understand why I am receiving this exception. This only happens when I have jobExecutorActivate set to "true" in the config. Just another note, this happen

Re: ActivitiOptimisticLockingException on even the simplest process

trademak — Fri, 06 Dec 2013 09:01:05 GMT

This exception will only happen if you have multiple Activiti Engines with the job executor activated. Because then they both retrieve the same job, but only one job executor will "win" and execute the job. Can you check if you have only one Activiti Engine running. If so please create a unit test project so we can reproduce it.

Best regards,

Re: ActivitiOptimisticLockingException on even the simplest process

jbrazil5 — Tue, 10 Dec 2013 15:52:04 GMT

I don't think I have multiple engines running. Could the issue be that I have multiple engines pointed at the same database? I have one database that I point all of my applications servers to. Does Activiti not support this configuration?

Re: ActivitiOptimisticLockingException on even the simplest process

brianok — Tue, 10 Dec 2013 17:15:38 GMT

I have this issue in 5.14 and I am using multiple engines. I am confused because a quick search seems to insinuate that clustering is not an issue. Maybe I haven't just read enough old threads yet, but is there a magic setting because right now it seems to be hanging up my subprocesses. I'll keep reading, but if you have any pointers, that would be useful.

Thanks in advance,
Brian

References:
http://forums.activiti.org/content/clustering
http://forums.activiti.org/content/could-multiple-activiti-engines-share-one-repository
http://forums.activiti.org/content/can-two-process-engines-run-same-database

Error:
org.activiti.engine.ActivitiOptimisticLockingException: VariableInstanceEntity[id=3272, name=nrOfCompletedInstances, type=integer, longValue=208, textValue=208] was updated by another transaction concurrently
        at org.activiti.engine.impl.db.DbSqlSession.flushUpdates(DbSqlSession.java:562)
        at org.activiti.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:444)
        at org.activiti.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:170)
        at org.activiti.engine.impl.interceptor.CommandContext.close(CommandContext.java:117)
        at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:66)
        at org.activiti.spring.SpringTransactionInterceptor$1.doInTransaction(SpringTransactionInterceptor.java:47)
        at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:131)
        at org.activiti.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:45)
        at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:31)
        at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:40)
        at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:35)
        at org.activiti.engine.impl.RuntimeServiceImpl.signal(RuntimeServiceImpl.java:188)
        at org.activiti.camel.ActivitiProducer.signal(ActivitiProducer.java:95)
        at org.activiti.camel.ActivitiProducer.process(ActivitiProducer.java:60)
        at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)

Re: ActivitiOptimisticLockingException on even the simplest process

brianok — Tue, 10 Dec 2013 17:32:48 GMT

Sorry, I should clarify that even though I am running multiple engines, this also seems to be happening in a single engine instance where I am running multi-instance over a collection (sequential = false).

Re: ActivitiOptimisticLockingException on even the simplest process

jbrazil5 — Tue, 10 Dec 2013 18:24:05 GMT

Is it possible that if one of my included libraries(using maven, including multiple libraries that are dependent on Activiti) also has an activiti.cfg.xml a second engine is being created without my knowledge?

Re: ActivitiOptimisticLockingException on even the simplest process

martin_grofcik — Wed, 11 Dec 2013 08:37:43 GMT

Can you create jUnit test for it?
http://forums.activiti.org/content/sticky-how-write-unit-test

Re: ActivitiOptimisticLockingException on even the simplest process

slav — Thu, 15 Jan 2015 16:07:17 GMT

Hello,

I'm sorry for posting to such an old topic, but have you come to any conclusion afterwards?
I am now facing pretty much the same problem.

I am updating Activiti version from 5.8 to 5.15.1 in an old Spring application, and now I'm getting this error in multiple test cases:
<blockcode>
16:25:47.527 ERROR [pool-1-thread-1] [ExecuteJobsRunnable] exception during job execution: JobEntity [id=67] was updated by another transaction concurrently
org.activiti.engine.ActivitiOptimisticLockingException: JobEntity [id=67] was updated by another transaction concurrently
at org.activiti.engine.impl.db.DbSqlSession$CheckedDeleteOperation.execute(DbSqlSession.java:272) ~[activiti-engine-5.15.1.jar:5.15.1]
at org.activiti.engine.impl.db.DbSqlSession.flushDeletes(DbSqlSession.java:635) ~[activiti-engine-5.15.1.jar:5.15.1]
at org.activiti.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:503) ~[activiti-engine-5.15.1.jar:5.15.1]
at org.activiti.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:175) ~[activiti-engine-5.15.1.jar:5.15.1]
at org.activiti.engine.impl.interceptor.CommandContext.close(CommandContext.java:122) ~[activiti-engine-5.15.1.jar:5.15.1]
at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:66) ~[activiti-engine-5.15.1.jar:5.15.1]
at org.activiti.spring.SpringTransactionInterceptor$1.doInTransaction(SpringTransactionInterceptor.java:47) ~[activiti-spring-5.15.1.jar:5.15.1]
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:131) ~[spring-tx-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.activiti.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:45) ~[activiti-spring-5.15.1.jar:5.15.1]
at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:31) ~[activiti-engine-5.15.1.jar:5.15.1]
at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:40) ~[activiti-engine-5.15.1.jar:5.15.1]
at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:35) ~[activiti-engine-5.15.1.jar:5.15.1]
at org.activiti.engine.impl.jobexecutor.ExecuteJobsRunnable.run(ExecuteJobsRunnable.java:52) ~[activiti-engine-5.15.1.jar:5.15.1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_72]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_72]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_72]
</blockcode>

I'm almost sure, that I have only one Activiti Engine running (unless there is any configuration option, in which you can set amount of running instances, which I'm not aware of).

I've checked many threads on this forum, but found no solution that would work in my case.

Please let me know, if there's any known commonly made mistake, or any version migration guidelines that might help me.

Thank you.

Re: ActivitiOptimisticLockingException on even the simplest process

trademak — Fri, 16 Jan 2015 11:38:16 GMT

Do you have a parallel gateway or multi instance in your process definition? We've revised the job executor quite a bit in 5.17.0, so you might want to read up in the user guide there.

Best regards,

Re: ActivitiOptimisticLockingException on even the simplest process

slav — Fri, 16 Jan 2015 13:14:32 GMT

Yes, I have parallel gateways in the process.

The reason why I don't use 5.17.0 is that I'd rather avoid Spring 4.0 in my Maven dependencies.

Anyway, I have tried to use 5.17.0, and I got the following stack trace:
<blockcode>
13:41:34.119 ERROR [pool-1-thread-3] [ExecuteJobsRunnable] exception during job execution: ProcessInstance[18] was updated by another transaction concurrently
org.activiti.engine.ActivitiOptimisticLockingException: ProcessInstance[18] was updated by another transaction concurrently
at org.activiti.engine.impl.db.DbSqlSession.flushUpdates(DbSqlSession.java:783) ~[activiti-engine-5.17.0.jar:5.17.0]
at org.activiti.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:594) ~[activiti-engine-5.17.0.jar:5.17.0]
at org.activiti.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:211) ~[activiti-engine-5.17.0.jar:5.17.0]
at org.activiti.engine.impl.interceptor.CommandContext.close(CommandContext.java:137) ~[activiti-engine-5.17.0.jar:5.17.0]
at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:66) ~[activiti-engine-5.17.0.jar:5.17.0]
at org.activiti.spring.SpringTransactionInterceptor$1.doInTransaction(SpringTransactionInterceptor.java:47) ~[activiti-spring-5.17.0.jar:5.17.0]
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:131) ~[spring-tx-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at org.activiti.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:45) ~[activiti-spring-5.17.0.jar:5.17.0]
at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:31) ~[activiti-engine-5.17.0.jar:5.17.0]
at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:40) ~[activiti-engine-5.17.0.jar:5.17.0]
at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:35) ~[activiti-engine-5.17.0.jar:5.17.0]
at org.activiti.engine.impl.jobexecutor.ExecuteJobsRunnable.handleMultipleJobs(ExecuteJobsRunnable.java:94) [activiti-engine-5.17.0.jar:5.17.0]
at org.activiti.engine.impl.jobexecutor.ExecuteJobsRunnable.run(ExecuteJobsRunnable.java:49) [activiti-engine-5.17.0.jar:5.17.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_72]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_72]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_72]
</blockcode>

So it seems, that there is still a problem in my process.

I just started using Activiti several days ago, so maye I have some basic mistakes in my process. Is there any change since 5.8, that might cause such problems?

Thank you.
Best regards,

EDIT:
It looks like using AsyncExecutor helps with this error.
I must still investigate, why some test cases fail, but it seems, that the cause is different now.

If I just may ask for one clarification: using AsyncExecutor will not change the outcome of the process - is that right?

Re: ActivitiOptimisticLockingException on even the simplest process

jbarrez — Fri, 16 Jan 2015 15:22:05 GMT

> Is there any change since 5.8, that might cause such problems?

5.8 has been released 3,5 years ago. I'd say yes

> using AsyncExecutor will not change the outcome of the process - is that right?

No, it's a replacement for the original job executor.