Timeout when create a lot of process in multi-instance

Camunda 7 Topics Discussion & Questions
,
1

Hi in my process I have script tasks that create at least 150 multi instance (parallel) User Task
So, I am suffering an error when I finish script tasks.
Image below cotains the error and process.

camunda rror
camunda rror2640×1390 877 KB

Log:
####<Dec 19, 2020 4:01:07,314 AM BRT> <org.camunda.bpm.engine.context> <[ACTIVE] ExecuteThread: ‘8’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <> <1608361267314> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <ENGINE-16004 Exception while closing command context: ENGINE-03004 Exception while executing Database Operation ‘INSERT HistoricActivityInstanceEventEntity[d273be9f-41c7-11eb-aa8d-0050568c84bb]’ with message ’
### Error updating database. Cause: java.sql.SQLException: The transaction is no longer active - status: ‘Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 61 seconds
BEA1-16F6704193F8BD4BDFDC]’. No further JDBC access is allowed within this transaction.
### The error may involve org.camunda.bpm.engine.impl.persistence.entity.HistoricActivityInstanceEntity.insertHistoricActivityInstanceEvent-Inline
### The error occurred while setting parameters
### SQL: insert into ACT_HI_ACTINST ( ID_, PARENT_ACT_INST_ID_, PROC_DEF_KEY_, PROC_DEF_ID_, ROOT_PROC_INST_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, CALL_CASE_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, ACT_INST_STATE_, SEQUENCE_COUNTER_, TENANT_ID_, REMOVAL_TIME_ ) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )
### Cause: java.sql.SQLException: The transaction is no longer active - status: ‘Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 61 seconds
BEA1-16F6704193F8BD4BDFDC]’. No further JDBC access is allowed within this transaction.’. Flush summary:
[
INSERT HistoricVariableInstanceEntity[d2778f31-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricVariableInstanceEntity[d27b86d5-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricJobLogEventEntity[d20d349d-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricJobLogEventEntity[d27d0d7c-41c7-11eb-aa8d-0050568c84bb]
INSERT AuthorizationEntity[d27c4a2b-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricVariableUpdateEventEntity[d2778f33-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricVariableUpdateEventEntity[d27b86d6-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricTaskInstanceEventEntity[d27bade8-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricProcessInstanceEventEntity[d273978e-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricIdentityLinkLogEventEntity[d27badea-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricActivityInstanceEventEntity[d273be9f-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricActivityInstanceEventEntity[d27bade7-41c7-11eb-aa8d-0050568c84bb]
INSERT ExecutionEntity[d273978e-41c7-11eb-aa8d-0050568c84bb]
INSERT TaskEntity[d27bade8-41c7-11eb-aa8d-0050568c84bb]
INSERT ByteArrayEntity[d2778f30-41c7-11eb-aa8d-0050568c84bb]
INSERT ByteArrayEntity[d2778f32-41c7-11eb-aa8d-0050568c84bb]
INSERT ByteArrayEntity[d2778f34-41c7-11eb-aa8d-0050568c84bb]
INSERT VariableInstanceEntity[d2778f31-41c7-11eb-aa8d-0050568c84bb]
INSERT VariableInstanceEntity[d27b86d5-41c7-11eb-aa8d-0050568c84bb]
INSERT TimerEntity[d20d349c-41c7-11eb-aa8d-0050568c84bb]
INSERT IdentityLinkEntity[d27bade9-41c7-11eb-aa8d-0050568c84bb]
DELETE TimerEntity[0c6a3701-41b7-11eb-aa8d-0050568c84bb]
]
org.camunda.bpm.engine.ProcessEngineException: ENGINE-03004 Exception while executing Database Operation ‘INSERT HistoricActivityInstanceEventEntity[d273be9f-41c7-11eb-aa8d-0050568c84bb]’ with message ’
### Error updating database. Cause: java.sql.SQLException: The transaction is no longer active - status: ‘Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 61 seconds
BEA1-16F6704193F8BD4BDFDC]’. No further JDBC access is allowed within this transaction.
### The error may involve org.camunda.bpm.engine.impl.persistence.entity.HistoricActivityInstanceEntity.insertHistoricActivityInstanceEvent-Inline
### The error occurred while setting parameters
### SQL: insert into ACT_HI_ACTINST ( ID_, PARENT_ACT_INST_ID_, PROC_DEF_KEY_, PROC_DEF_ID_, ROOT_PROC_INST_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, CALL_CASE_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, DURATION_, ACT_INST_STATE_, SEQUENCE_COUNTER_, TENANT_ID_, REMOVAL_TIME_ ) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )
### Cause: java.sql.SQLException: The transaction is no longer active - status: ‘Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 61 seconds
BEA1-16F6704193F8BD4BDFDC]’. No further JDBC access is allowed within this transaction.’. Flush summary:
[
INSERT HistoricVariableInstanceEntity[d2778f31-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricVariableInstanceEntity[d27b86d5-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricJobLogEventEntity[d20d349d-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricJobLogEventEntity[d27d0d7c-41c7-11eb-aa8d-0050568c84bb]
INSERT AuthorizationEntity[d27c4a2b-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricVariableUpdateEventEntity[d2778f33-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricVariableUpdateEventEntity[d27b86d6-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricTaskInstanceEventEntity[d27bade8-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricProcessInstanceEventEntity[d273978e-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricIdentityLinkLogEventEntity[d27badea-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricActivityInstanceEventEntity[d273be9f-41c7-11eb-aa8d-0050568c84bb]
INSERT HistoricActivityInstanceEventEntity[d27bade7-41c7-11eb-aa8d-0050568c84bb]
INSERT ExecutionEntity[d273978e-41c7-11eb-aa8d-0050568c84bb]
INSERT TaskEntity[d27bade8-41c7-11eb-aa8d-0050568c84bb]
INSERT ByteArrayEntity[d2778f30-41c7-11eb-aa8d-0050568c84bb]
INSERT ByteArrayEntity[d2778f32-41c7-11eb-aa8d-0050568c84bb]
INSERT ByteArrayEntity[d2778f34-41c7-11eb-aa8d-0050568c84bb]
INSERT VariableInstanceEntity[d2778f31-41c7-11eb-aa8d-0050568c84bb]
INSERT VariableInstanceEntity[d27b86d5-41c7-11eb-aa8d-0050568c84bb]
INSERT TimerEntity[d20d349c-41c7-11eb-aa8d-0050568c84bb]
INSERT IdentityLinkEntity[d27bade9-41c7-11eb-aa8d-0050568c84bb]
DELETE TimerEntity[0c6a3701-41b7-11eb-aa8d-0050568c84bb]
]

CAMUNDA version 7.12.0

2

Hi @mtonin,

Please format your post to make it more readable. You can check the style guide for more information on how to do it.

From what I can see in the logs, it seems that your transaction is timing out after 61 seconds, and any additional operations within that transaction are canceled, and the transaction is rolled back.

I would suggest checking the Database Server transaction timeout, or if you have set a client-side transaction time-out on the JDBC driver.

Alternatively, you can try to introduce transaction boundaries in your process, so that different parts of your process may be executed in different transactions. You can read more about this topic here: Transactions in Processes | docs.camunda.org

Best,
Nikola