Flowable Table Locking issue

sameer.uppal · July 19, 2021, 11:00am

Hi Team
Getting below error.
org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.insertHistoricActivityInstance-Inline

org.apache.ibatis.exceptions.PersistenceException:

Error updating database. Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.insertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values ( ?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )

Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

    at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:30)
    at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:199)
    at org.apache.ibatis.session.defaults.DefaultSqlSession.insert(DefaultSqlSession.java:184)
    at org.flowable.common.engine.impl.db.DbSqlSession.flushRegularInsert(DbSqlSession.java:509)
    at org.flowable.common.engine.impl.db.DbSqlSession.flushInsertEntities(DbSqlSession.java:493)
    at org.flowable.common.engine.impl.db.DbSqlSession.flushInserts(DbSqlSession.java:473)
    at org.flowable.common.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:358)
    at org.flowable.common.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:192)
    at org.flowable.common.engine.impl.interceptor.CommandContext.close(CommandContext.java:61)
    at org.flowable.common.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:81)
    at org.flowable.common.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:51)
    at org.flowable.common.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30)
    at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:56)
    at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:51)
    at org.flowable.engine.impl.RuntimeServiceImpl.startProcessInstance(RuntimeServiceImpl.java:732)
    at org.flowable.engine.impl.runtime.ProcessInstanceBuilderImpl.start(ProcessInstanceBuilderImpl.java:205)
    at com.techm.bm.om.orderdecompositionservice.services.WorkflowService.startProcess(WorkflowService.java:134)
    at com.techm.bm.om.orderdecompositionservice.consumer.ServiceOrderCreatedEventHandler.on(ServiceOrderCreatedEventHandler.java:86)
    at sun.reflect.GeneratedMethodAccessor830.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.axonframework.messaging.annotation.AnnotatedMessageHandlingMember.handle(AnnotatedMessageHandlingMember.java:132)
    at org.axonframework.eventhandling.AnnotationEventHandlerAdapter.handle(AnnotationEventHandlerAdapter.java:91)
    at org.axonframework.eventhandling.SimpleEventHandlerInvoker.handle(SimpleEventHandlerInvoker.java:108)
    at org.axonframework.eventhandling.MultiEventHandlerInvoker.handle(MultiEventHandlerInvoker.java:89)
    at org.axonframework.eventhandling.AbstractEventProcessor.lambda$null$1(AbstractEventProcessor.java:165)
    at org.axonframework.messaging.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:57)
    at org.axonframework.messaging.interceptors.CorrelationDataInterceptor.handle(CorrelationDataInterceptor.java:65)
    at org.axonframework.messaging.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:55)
    at org.axonframework.eventhandling.TrackingEventProcessor.lambda$new$1(TrackingEventProcessor.java:181)
    at org.axonframework.messaging.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:55)
    at org.axonframework.eventhandling.AbstractEventProcessor.lambda$processInUnitOfWork$2(AbstractEventProcessor.java:173)
    at org.axonframework.messaging.unitofwork.BatchingUnitOfWork.executeWithResult(BatchingUnitOfWork.java:86)
    at org.axonframework.eventhandling.AbstractEventProcessor.processInUnitOfWork(AbstractEventProcessor.java:159)
    at org.axonframework.eventhandling.TrackingEventProcessor.processBatch(TrackingEventProcessor.java:438)
    at org.axonframework.eventhandling.TrackingEventProcessor.processingLoop(TrackingEventProcessor.java:301)
    at org.axonframework.eventhandling.TrackingEventProcessor$TrackingSegmentWorker.run(TrackingEventProcessor.java:1161)
    at org.axonframework.eventhandling.TrackingEventProcessor$WorkerLauncher.run(TrackingEventProcessor.java:1276)
    at java.lang.Thread.run(Thread.java:748)

Caused by: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction
at org.mariadb.jdbc.internal.util.exceptions.ExceptionFactory.createException(ExceptionFactory.java:79)
at org.mariadb.jdbc.internal.util.exceptions.ExceptionFactory.create(ExceptionFactory.java:153)
at org.mariadb.jdbc.MariaDbStatement.executeExceptionEpilogue(MariaDbStatement.java:273)
at org.mariadb.jdbc.ClientSidePreparedStatement.executeInternal(ClientSidePreparedStatement.java:229)
at org.mariadb.jdbc.ClientSidePreparedStatement.execute(ClientSidePreparedStatement.java:149)
at com.zaxxer.hikari.pool.ProxyPreparedStatement.execute(ProxyPreparedStatement.java:44)
at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.execute(HikariProxyPreparedStatement.java)
at org.apache.ibatis.executor.statement.PreparedStatementHandler.update(PreparedStatementHandler.java:47)
at org.apache.ibatis.executor.statement.RoutingStatementHandler.update(RoutingStatementHandler.java:74)
at org.apache.ibatis.executor.SimpleExecutor.doUpdate(SimpleExecutor.java:50)
at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:117)
at org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:76)
at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:197)
… 37 common frames omitted
Caused by: org.mariadb.jdbc.internal.util.exceptions.MariaDbSqlException: Lock wait timeout exceeded; try restarting transaction
at org.mariadb.jdbc.internal.util.exceptions.MariaDbSqlException.of(MariaDbSqlException.java:34)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.exceptionWithQuery(AbstractQueryProtocol.java:194)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.exceptionWithQuery(AbstractQueryProtocol.java:177)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.executeQuery(AbstractQueryProtocol.java:321)
at org.mariadb.jdbc.ClientSidePreparedStatement.executeInternal(ClientSidePreparedStatement.java:220)
… 46 common frames omitted
Caused by: java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readErrorPacket(AbstractQueryProtocol.java:1674)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readPacket(AbstractQueryProtocol.java:1536)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.getResult(AbstractQueryProtocol.java:1499)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.executeQuery(AbstractQueryProtocol.java:318)
… 47 common frames omitted

2021-07-19 10:23:11.769 ERROR 7 — [tion-process]-0] .b.o.o.c.ServiceOrderCreatedEventHandler :

Error updating database. Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.insertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values ( ?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )

Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

org.apache.ibatis.exceptions.PersistenceException:

Error updating database. Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.insertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values ( ?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )

Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

    at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:30)
    at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:199)
    at org.apache.ibatis.session.defaults.DefaultSqlSession.insert(DefaultSqlSession.java:184)
    at org.flowable.common.engine.impl.db.DbSqlSession.flushRegularInsert(DbSqlSession.java:509)
    at org.flowable.common.engine.impl.db.DbSqlSession.flushInsertEntities(DbSqlSession.java:493)
    at org.flowable.common.engine.impl.db.DbSqlSession.flushInserts(DbSqlSession.java:473)
    at org.flowable.common.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:358)
    at org.flowable.common.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:192)
    at org.flowable.common.engine.impl.interceptor.CommandContext.close(CommandContext.java:61)
    at org.flowable.common.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:81)
    at org.flowable.common.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:51)
    at org.flowable.common.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30)
    at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:56)
    at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:51)
    at org.flowable.engine.impl.RuntimeServiceImpl.startProcessInstance(RuntimeServiceImpl.java:732)
    at org.flowable.engine.impl.runtime.ProcessInstanceBuilderImpl.start(ProcessInstanceBuilderImpl.java:205)
    at com.techm.bm.om.orderdecompositionservice.services.WorkflowService.startProcess(WorkflowService.java:134)
    at com.techm.bm.om.orderdecompositionservice.consumer.ServiceOrderCreatedEventHandler.on(ServiceOrderCreatedEventHandler.java:86)
    at sun.reflect.GeneratedMethodAccessor830.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.axonframework.messaging.annotation.AnnotatedMessageHandlingMember.handle(AnnotatedMessageHandlingMember.java:132)
    at org.axonframework.eventhandling.AnnotationEventHandlerAdapter.handle(AnnotationEventHandlerAdapter.java:91)
    at org.axonframework.eventhandling.SimpleEventHandlerInvoker.handle(SimpleEventHandlerInvoker.java:108)
    at org.axonframework.eventhandling.MultiEventHandlerInvoker.handle(MultiEventHandlerInvoker.java:89)
    at org.axonframework.eventhandling.AbstractEventProcessor.lambda$null$1(AbstractEventProcessor.java:165)
    at org.axonframework.messaging.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:57)
    at org.axonframework.messaging.interceptors.CorrelationDataInterceptor.handle(CorrelationDataInterceptor.java:65)
    at org.axonframework.messaging.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:55)
    at org.axonframework.eventhandling.TrackingEventProcessor.lambda$new$1(TrackingEventProcessor.java:181)
    at org.axonframework.messaging.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:55)
    at org.axonframework.eventhandling.AbstractEventProcessor.lambda$processInUnitOfWork$2(AbstractEventProcessor.java:173)
    at org.axonframework.messaging.unitofwork.BatchingUnitOfWork.executeWithResult(BatchingUnitOfWork.java:86)
    at org.axonframework.eventhandling.AbstractEventProcessor.processInUnitOfWork(AbstractEventProcessor.java:159)
    at org.axonframework.eventhandling.TrackingEventProcessor.processBatch(TrackingEventProcessor.java:438)
    at org.axonframework.eventhandling.TrackingEventProcessor.processingLoop(TrackingEventProcessor.java:301)
    at org.axonframework.eventhandling.TrackingEventProcessor$TrackingSegmentWorker.run(TrackingEventProcessor.java:1161)
    at org.axonframework.eventhandling.TrackingEventProcessor$WorkerLauncher.run(TrackingEventProcessor.java:1276)
    at java.lang.Thread.run(Thread.java:748)

Caused by: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction
at org.mariadb.jdbc.internal.util.exceptions.ExceptionFactory.createException(ExceptionFactory.java:79)
at org.mariadb.jdbc.internal.util.exceptions.ExceptionFactory.create(ExceptionFactory.java:153)
at org.mariadb.jdbc.MariaDbStatement.executeExceptionEpilogue(MariaDbStatement.java:273)
at org.mariadb.jdbc.ClientSidePreparedStatement.executeInternal(ClientSidePreparedStatement.java:229)
at org.mariadb.jdbc.ClientSidePreparedStatement.execute(ClientSidePreparedStatement.java:149)
at com.zaxxer.hikari.pool.ProxyPreparedStatement.execute(ProxyPreparedStatement.java:44)
at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.execute(HikariProxyPreparedStatement.java)
at org.apache.ibatis.executor.statement.PreparedStatementHandler.update(PreparedStatementHandler.java:47)
at org.apache.ibatis.executor.statement.RoutingStatementHandler.update(RoutingStatementHandler.java:74)
at org.apache.ibatis.executor.SimpleExecutor.doUpdate(SimpleExecutor.java:50)
at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:117)
at org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:76)
at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:197)
… 37 common frames omitted
Caused by: org.mariadb.jdbc.internal.util.exceptions.MariaDbSqlException: Lock wait timeout exceeded; try restarting transaction
at org.mariadb.jdbc.internal.util.exceptions.MariaDbSqlException.of(MariaDbSqlException.java:34)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.exceptionWithQuery(AbstractQueryProtocol.java:194)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.exceptionWithQuery(AbstractQueryProtocol.java:177)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.executeQuery(AbstractQueryProtocol.java:321)
at org.mariadb.jdbc.ClientSidePreparedStatement.executeInternal(ClientSidePreparedStatement.java:220)
… 46 common frames omitted
Caused by: java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readErrorPacket(AbstractQueryProtocol.java:1674)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.readPacket(AbstractQueryProtocol.java:1536)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.getResult(AbstractQueryProtocol.java:1499)
at org.mariadb.jdbc.internal.protocol.AbstractQueryProtocol.executeQuery(AbstractQueryProtocol.java:318)
… 47 common frames omitted

2021-07-19 10:23:12.315 WARN 7 — [tion-process]-0] o.a.e.TrackingEventProcessor : Error occurred. Starting retry mode.

javax.management.RuntimeErrorException:

Error updating database. Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.insertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values ( ?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )

Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

    at com.techm.bm.om.orderdecompositionservice.consumer.ServiceOrderCreatedEventHandler.on(ServiceOrderCreatedEventHandler.java:90)

joram · August 2, 2021, 7:53am

This typically means the database can’t handle the load it needs to handle: a lock was taken but the work wasn’t completed in the timeout period.

Can you share more about which database / it’s setup? And how much concurrency / type of load you have?

sameer.uppal · August 2, 2021, 11:17am

@joram thanks for reply. we are using MariaDb and currently having 10 concurrent user but facing this lock issue sometime.
please suggest someone to resolve this issue,

joram · August 2, 2021, 1:17pm

With 10 users, you should hardly be giving the database a sweat. How is your database setup (hardware-wise), did you configure your connection pool settings, any config that might help us?

ROY · November 15, 2022, 10:51am

HI @sameer.uppal I am also having the same issue. can you please let me know how you solved the issue.

@joram I am using Mysql which is running on Linux and flowable also runs on the same server
RAM 128 and CPU 32
with innodb_lock_wait_timetout = 50

joram · November 23, 2022, 9:32am

What kind of load / logic are you executing on it? Did you give the db enough resources (the server can have 128 gb ram, but mysql also needs to be configured to use it).

ROY · November 23, 2022, 4:22pm

HI Joram,

The load of the execution : 1000+ models connected in a flow and which involves a couple of multi-instance

i have configured mysql with below parameters
innodb-buffer-pool-size=21474836480
innodb_buffer_pool_instances=20
innodb_log_file_size=4294967296
sort_buffer_size = 50M
read_rnd_buffer_size = 50M
join_buffer_size = 256M
innodb_log_buffer_size = 167772160
innodb_sort_buffer_size = 10485760
innodb_read_io_threads = 16
innodb_write_io_threads = 16
innodb_status_output = ON
innodb_status_output_locks = ON
innodb_rollback_on_timeout = ON

with my further analysis what I understood is
Once the lock issue starts then on one of thread is acquiring the jobs but is not processing it. so the execution is also stuck

Regards,
Febin Roy

ROY · November 27, 2022, 6:40pm

in database logs i can see the deadlock is created by the below query

delete BYTES_
from ACT_GE_BYTEARRAY BYTES_
where BYTES_.ID_ in (
select RES.BATCH_DOC_ID_
from FLW_RU_BATCH RES
WHERE RES.TYPE_ = ‘historicProcessDelete’
and RES.COMPLETE_TIME_ < ‘2021-11-25 07:00:44.744’

            and RES.BATCH_DOC_ID_ is not null
             and RES.BATCH_DOC_ID_ != ''
        union all
        select PARTS_.RESULT_DOC_ID_
        from FLW_RU_BATCH_PART PARTS_
        where PARTS_.RESULT_DOC_ID_ is not null
             and PARTS_.RESULT_DOC_ID_ != ''
            and PARTS_.BATCH_ID_ in (
                select RES.ID_
    from FLW_RU_BATCH RES
     WHERE  RES.TYPE_ = 'historicProcessDelete'

joram · November 29, 2022, 8:06am

That looks like the housekeeping deletion query. I’m assuming you have a lot of historical data? What settings do you have for the housekeeping?

Note: in the upcoming 6.8.0 version we have improved the performance of the housekeeping. On huge tables with aggressive parameters, it could be before that the database can’t cope with the load being put on it (hence the deadlock exception).

Topic		Replies	Views
Deadlock ActivityInstanceEntityImpl.updateActivityInstance-Inline Flowable Engine	4	964	October 1, 2020
Job acquisition is not happening in flowable Flowable Engine	5	567	November 29, 2022
Publish not working because Lock wait timeout Flowable Engine	8	1875	March 14, 2018
Strange db locks on mysql Flowable Engine	3	1287	November 10, 2021
Deadlock found when complete task (flowable 6.5, mysql 5.6) Flowable Engine	1	1287	June 19, 2020

Flowable Table Locking issue

Error updating database. Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.insertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values ( ?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )

Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

Error updating database. Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.insertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values ( ?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )

Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

Error updating database. Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.insertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values ( ?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )

Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

Error updating database. Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.insertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values ( ?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )

Cause: java.sql.SQLTransientConnectionException: (conn=1860579) Lock wait timeout exceeded; try restarting transaction

Related topics