-
Type:
Task
-
Resolution: Fixed
-
Priority:
L3 - Default
-
Affects Version/s: 7.13.0
-
Component/s: None
-
None
root cause:
- The server ran out of transaction logs space. The necessary size can be calculated with this formula (search for "server transaction logs").
solution:
- Increase the space for transaction logs either dynamically at runtime or by a sensible amount for the affected tests with large data sets.
further information:
- Error Code: -4229
- https://ci.cambpm.camunda.cloud/view/Seed-Jobs/job/7.13/job/7.13-platform-PERFORMANCE-large-data-db2-111/
08:46:14 at org.camunda.bpm.qa.largedata.optimize.OptimizeApiPageSizeTest.init(OptimizeApiPageSizeTest.java:51) 08:46:14 Caused by: org.apache.ibatis.exceptions.PersistenceException: 08:46:14 08:46:14 ### Error flushing statements. Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.persistence.entity.HistoricActivityInstanceEntity.insertHistoricActivityInstanceEvent (batch index #1) failed. Cause: com.ibm.db2.jcc.am.BatchUpdateException: [jcc][t4][102][10040][4.22.29] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. 08:46:14 Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null 08:46:14 ### Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.persistence.entity.HistoricActivityInstanceEntity.insertHistoricActivityInstanceEvent (batch index #1) failed. Cause: com.ibm.db2.jcc.am.BatchUpdateException: [jcc][t4][102][10040][4.22.29] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.
- is related to
-
CAM-11788 Failing tests for larger data set
-
- Closed
-