[CAM-6104] Batch migration fails with timeout on developer VM Created: 25/May/16 Updated: 25/May/16 Resolved: 25/May/16 Status: Project: Component/s: Affects Version/s: Fix Version/s: Closed camunda BPM engine None Type: Reporter: Resolution: Labels: Remaining Estimate: Time Spent: Original Estimate: Environment: Bug Report Matthijs Burke Cannot Reproduce None Not Specified None Priority: Assignee: Votes: L3 - Default Matthijs Burke 0 Not Specified Not Specified WebSphere 8.5 DB2 for Linux, UNIX and Windows version 10.5 JDBC 3.0.0 Attachments: websphere-batch-migration.PNG Description What are the steps to reproduce your problem? Perform multiple batch migrations sequentially What is the problem? A job fails with the following exception: org.camunda.bpm.engine.ProcessEngineException: ENGINE-03004 Exception while executing Data ExecutionEntity[d3e4f501-2259-11e6-8bd7-080027862a37]' with message ' ### Error updating database. Cause: com.ibm.db2.jcc.am.SqlTransactionRollbackException: D rückgängig gemacht. Ursache: Deadlock oder Zeitüberschreitung. Ursachencode: "2".. SQ DRIVER=4.13.111 ### The error may involve org.camunda.bpm.engine.impl.persistence.entity.ExecutionEntity.u ### The error occurred while setting parameters ### SQL: update ACT_RU_EXECUTION set REV_ = ?, PROC_DEF_ID_ = ?, ACT_ID_ IS_ACTIVE_ = ?, IS_CONCURRENT_ = ?, IS_SCOPE_ = ?, IS_EVENT_SCOPE_ = ?, = ?, SUSPENSION_STATE_ = ?, CACHED_ENT_STATE_ = ?, SEQUENCE_COUNTER_ = ? and REV_ = ? ### Cause: com.ibm.db2.jcc.am.SqlTransactionRollbackException: Die aktuelle Transaktion wu Deadlock oder Zeitüberschreitung. Ursachencode: "2".. SQLCODE=-911, SQLSTATE=40001, DRIV [ INSERT HistoricJobLogEventEntity[9ff2f767-225a-11e6-8bd7-080027862a37] INSERT ByteArrayEntity[9ff23415-225a-11e6-8bd7-080027862a37] INSERT ByteArrayEntity[9ff28236-225a-11e6-8bd7-080027862a37] DELETE MessageEntity[966c2745-225a-11e6-8bd7-080027862a37] DELETE ByteArrayEntity[966c2744-225a-11e6-8bd7-080027862a37] DELETE_BULK deleteByteArrayNoRevisionCheck 9c673884-225a-11e6-8bd7-080027862a37 DELETE_BULK deleteByteArrayNoRevisionCheck 7d2a8bd1-225a-11e6-8bd7-080027862a37 DELETE_BULK deleteByteArrayNoRevisionCheck 7d2a3db0-225a-11e6-8bd7-080027862a37 DELETE_BULK deleteByteArrayNoRevisionCheck 966c2744-225a-11e6-8bd7-080027862a37 UPDATE TaskEntity[d3e60690-2259-11e6-8bd7-080027862a37] UPDATE ExecutionEntity[d3e4f501-2259-11e6-8bd7-080027862a37] UPDATE HistoricActivityInstanceEventEntity[approveInvoice:d3e6068f-2259-11e6-8bd7-080027 UPDATE HistoricProcessInstanceEventEntity[d3e4f501-2259-11e6-8bd7-080027862a37] UPDATE HistoricTaskInstanceEventEntity[d3e60690-2259-11e6-8bd7-080027862a37] UPDATE HistoricVariableInstanceEntity[d3e51c13-2259-11e6-8bd7-080027862a37] UPDATE HistoricVariableInstanceEntity[d3e51c15-2259-11e6-8bd7-080027862a37] UPDATE HistoricVariableInstanceEntity[d3e51c16-2259-11e6-8bd7-080027862a37] UPDATE HistoricVariableInstanceEntity[d3e51c17-2259-11e6-8bd7-080027862a37] UPDATE HistoricVariableInstanceEntity[d3e51c18-2259-11e6-8bd7-080027862a37] UPDATE HistoricVariableInstanceEntity[d3e6068b-2259-11e6-8bd7-080027862a37] ] at org.camunda.bpm.engine.impl.db.EnginePersistenceLogger.flushDbOperationExceptio at org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.flushDbOperationMa at org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.flush(DbEntityMana at org.camunda.bpm.engine.impl.interceptor.CommandContext.flushSessions(CommandCon at org.camunda.bpm.engine.impl.interceptor.CommandContext.close(CommandContext.jav at org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(Comma at org.camunda.bpm.engine.spring.SpringTransactionInterceptor$1.doInTransaction(Sp at org.springframework.transaction.jta.WebSphereUowTransactionManager$UOWActionAdapter.run(We at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderNewUOW(EmbeddableUOW at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderUOW(EmbeddableUOWMan at org.springframework.transaction.jta.WebSphereUowTransactionManager.execute(WebS at org.springframework.transaction.support.TransactionTemplate.execute(Transaction at org.camunda.bpm.engine.spring.SpringTransactionInterceptor.execute(SpringTransa at org.camunda.bpm.engine.impl.interceptor.ProcessApplicationContextInterceptor.execute(Proce at org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.j at org.camunda.bpm.container.impl.ejb.JobExecutionHandlerMDB.executeJob(JobExecuti at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja at java.lang.reflect.Method.invoke(Method.java:611) at com.ibm.ws.ejbcontainer.mdb.MessageEndpointHandler.invokeMdbMethod(MessageEndpo at com.ibm.ws.ejbcontainer.mdb.MessageEndpointHandler.invoke(MessageEndpointHandle at com.sun.proxy.$Proxy36.executeJob(Unknown Source) at org.camunda.bpm.container.impl.threading.ra.inflow.JcaInflowExecuteJobsRunnable.executeJob at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobsRunnable.run(ExecuteJobsRunn at org.camunda.bpm.container.impl.threading.ra.commonj.CommonjWorkRunnableAdapter. at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1178) at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContext at com.ibm.ws.asynchbeans.CJWorkItemImpl.run(CJWorkItemImpl.java:236) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862) Caused by: org.apache.ibatis.exceptions.PersistenceException: ### Error updating database. Cause: com.ibm.db2.jcc.am.SqlTransactionRollbackException: D rückgängig gemacht. Ursache: Deadlock oder Zeitüberschreitung. Ursachencode: "2".. SQ DRIVER=4.13.111 ### The error may involve org.camunda.bpm.engine.impl.persistence.entity.ExecutionEntity.u ### The error occurred while setting parameters ### SQL: update ACT_RU_EXECUTION set REV_ = ?, PROC_DEF_ID_ = ?, ACT_ID_ IS_ACTIVE_ = ?, IS_CONCURRENT_ = ?, IS_SCOPE_ = ?, IS_EVENT_SCOPE_ = ?, = ?, SUSPENSION_STATE_ = ?, CACHED_ENT_STATE_ = ?, SEQUENCE_COUNTER_ = ? and REV_ = ? ### Cause: com.ibm.db2.jcc.am.SqlTransactionRollbackException: Die aktuelle Transaktion wu Deadlock oder Zeitüberschreitung. Ursachencode: "2".. SQLCODE=-911, SQLSTATE=40001, DRIV at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.ja at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.j at org.camunda.bpm.engine.impl.db.sql.DbSqlSession.executeUpdate(DbSqlSession.java at org.camunda.bpm.engine.impl.db.sql.DbSqlSession.updateEntity(DbSqlSession.java: at org.camunda.bpm.engine.impl.db.AbstractPersistenceSession.executeDbOperation(Ab at org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.flushDbOperationMa ... 28 more Caused by: com.ibm.db2.jcc.am.SqlTransactionRollbackException: Die aktuelle Transaktion wu Deadlock oder Zeitüberschreitung. Ursachencode: "2".. SQLCODE=-911, SQLSTATE=40001, DRIV at com.ibm.db2.jcc.am.id.a(id.java:664) at com.ibm.db2.jcc.am.id.a(id.java:60) at com.ibm.db2.jcc.am.id.a(id.java:127) at com.ibm.db2.jcc.am.fo.c(fo.java:2653) at com.ibm.db2.jcc.t4.cb.t(cb.java:982) at com.ibm.db2.jcc.t4.cb.l(cb.java:405) at com.ibm.db2.jcc.t4.cb.a(cb.java:62) at com.ibm.db2.jcc.t4.q.a(q.java:50) at com.ibm.db2.jcc.t4.tb.b(tb.java:220) at com.ibm.db2.jcc.am.go.oc(go.java:3428) at com.ibm.db2.jcc.am.go.b(go.java:4383) at com.ibm.db2.jcc.am.go.ic(go.java:2767) at com.ibm.db2.jcc.am.go.execute(go.java:2747) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecute(WSJdbcPreparedStat at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.execute(WSJdbcPreparedStateme at org.apache.ibatis.executor.statement.PreparedStatementHandler.update(PreparedSt at org.apache.ibatis.executor.statement.RoutingStatementHandler.update(RoutingStat at org.apache.ibatis.executor.SimpleExecutor.doUpdate(SimpleExecutor.java:48) at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:105) at org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:71) at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.j ... 32 more One instance is not migrated What would be the expected behavior: Batch migration completes successfully for all instances without exceptions Hints (optional): Information about batch takes a long time to load (see attached screenshot) Tested with latest Snapshot (camunda-bpm-websphere-7.5.0-20160524.203039-1236) on developer VM websphere + DB2 Generated at Wed Apr 05 13:09:31 CEST 2017 using JIRA 6.4.6#64021sha1:33e5b454af4594f54560ac233c30a6e00459507e.