Updating an issue causes TransactionRuntimeException or "current transaction is aborted" errors

Issue Summary

When a node tries to register a cluster lock, it will try to register it in a local memory, and then register it in the database, which we expect may fail as another node may have already created this entry.

The problem happens if this code (that is creating the cluster lock) is executed within an existing database transaction. In that case, the whole transaction is marked to be rolled back, rather than accepting the error as part of the algorithm.

Environment

• Jira Data Center 8.3+

Steps to Reproduce

This issue can be reproduced with regular actions such as:

• archiving multiple issues in a row.
• transitioning issues.

Expected Results

Operations would complete with no errors.

Actual Results

Users may see an error on the screen:

These exceptions are thrown in the atlassian-jira.log file:

ERROR: current transaction is aborted, commands ignored until end of transaction block

com.atlassian.jira.transaction.TransactionRuntimeException: org.ofbiz.core.entity.GenericTransactionException: Commit failed, rollback previously requested by nested transaction.

ERROR: duplicate key value violates unique constraint "cluster_lock_name_idx"
  Detail: Key (lock_name)=(sla_issue_update_51855) already exists.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available