Frequent deadlocks are reported by (Oracle) DB when accessing the capability table.
Databases wait to actually write (flush) data until someone wants to read it.
The hibernate session is being flushed and for some reason the capability object is marked as dirty.
Hibernate issues an update to persist the capability. Not usually a big deal but with a large number of plans and the fact that this is invoked from an event, we could have events that try to lock competing resources.
[BAM-5456] CAPABILITY and NOTIFICATIONS table access with Empty values causes (Oracle) Deadlock in larger instances
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1434837 ] | New: JAC Bug Workflow v3 [ 3379363 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1409056 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1434837 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 610001 ] | New: Bamboo Workflow 2016 v1 [ 1409056 ] |
Workflow | Original: Bamboo Workflow 2014 [ 605049 ] | New: Bamboo Workflow 2014 v2 [ 610001 ] |
Workflow | Original: Bamboo Workflow 2010 [ 207424 ] | New: Bamboo Workflow 2014 [ 605049 ] |
Fix Version/s | New: 2.6 [ 15056 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: To be reviewed [ 10026 ] | New: Resolved [ 5 ] |
Remaining Estimate | Original: 11h 20m [ 40800 ] | New: 11.1h [ 39960 ] |
Time Spent | Original: 40m [ 2400 ] | New: 0.9h [ 3240 ] |
in https://support.atlassian.com/browse/BSP-2836 non-existing Notification Recipients are stored as StringUtils.EMPTY in the NOTIFICATIONS table.