The batch update is failing from the release MariaDB 10.2.x.
It is because of the latest release of MariaDB driver (mariadb-java-client).

Everything is working fine till MariaDB driver 2.0.3 release.

From MariaDB driver 2.1 the problem started with MariaDB 10.2.x.

We are using MariaDB 10.2.x with our Camunda Application.
Once we submit the flushResults() request to the DB, we are getting the below error from DB.

An error happened while submitting the task form :
Cannot submit task form <task-id>: ENGINE-<engine-id> Execution of ‘UPDATE ExecutionEntity[entity-id]’ failed. Entity was updated by another transaction concurrently.

It is throwing optimistic locking Exception.

Transaction log :

2 lock struct(s), heap size 1136, 1 row lock(s), undo log entries 1
MySQL thread id 3508, OS thread handle 140480266315520, query id 56760 demo cleaning up
Trx read view will not see trx with id >= 10270, sees < 10269
TABLE LOCK table db03.ACT_GE_PROPERTY trx id 10270 lock mode IX
RECORD LOCKS space id 224 page no 3 n bits 80 index PRIMARY of table db03.ACT_GE_PROPERTY trx id 10270 lock_mode X locks rec but not gap
Record lock, heap no 14 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
0: len 9; hex 6e6578742e64626964; asc next.dbid;;
1: len 6; hex 00000000281e; asc ( ;;
2: len 7; hex 4e0000021628f0; asc N ( ;;
3: len 3; hex 323031; asc 201;;
4: len 4; hex 80000003; asc ;;

—TRANSACTION 10269, ACTIVE 2328 sec
2 lock struct(s), heap size 1136, 1 row lock(s)
MySQL thread id 3504, OS thread handle 140481065899776, query id 56744 demo cleaning up
TABLE LOCK table db03.ACT_GE_PROPERTY trx id 10269 lock mode IX
RECORD LOCKS space id 224 page no 3 n bits 80 index PRIMARY of table db03.ACT_GE_PROPERTY trx id 10269 lock_mode X locks rec but not gap
Record lock, heap no 5 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
0: len 15; hex 6465706c6f796d656e742e6c6f636b; asc deployment.lock;;
1: len 6; hex 000000001f17; asc ;;
2: len 7; hex f6000001dd0150; asc P;;
3: len 1; hex 30; asc 0;;
4: len 4; hex 80000001; asc ;;