MySQL default transaction level for Automation for Jira queries is wrong

Description

MySQL by default uses REPEATABLE READ as it's transaction isolation level. Every other DB uses READ COMMITTED.

We falsely assumed that Jira's DBConnectionManager we use was setting this transaction level, but it turns out this is not the case.

This can lead to MySQLTransactionRollbackException exceptions due to deadlocks in mysql.

Environment

None

Status

Assignee

Andreas Knecht

Reporter

Andreas Knecht

Links

1

Fix versions

Priority