-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
7.7.1.GA
-
2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19)
When trying to perform bulk task operation(start/complete) then it fails with below exception:
2020-07-28 15:01:35,221 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (default task-1282) SQL Error: -803, SQLState: 23505 2020-07-28 15:01:35,221 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (default task-1282) DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=1;$SCHEMA_NAME.ORGANIZATIONALENTITY, DRIVER=4.19.66 2020-07-28 15:01:35,222 WARN [org.jbpm.services.task.persistence.TaskTransactionInterceptor] (default task-1282) Could not commit session: javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not execute statement
This issue occurs when task operation is performed by new users in parallel by multiple threads. This issue can be avoided by these two options:
- Update the database with this new user entry before the bulk task operation
- Complete a single task operation request first and then send the rest of the requests in parallel.
But when ConstraintViolationException occurs, it makes the Task table and TaskEvent table entries out of sync.
For same Task_id in Task table state is 'Completed' and in TaskEvent table it shows STARTED(i.e InProgress) status.
- is documented by
-
BXMSDOC-7083 Document runtime users for user tasks
- Open
- is related to
-
RHPAM-3286 User task can cause race condition when multiple threads/process are storing the same org entity for the first time.
- Closed
- relates to
-
JBPM-9371 Task table is not in sync with TaskEvent table.
- Pull Request Sent