Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-22147

ExpirableResettableLazyCloseableReference can deadlock

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 9.3.0, 9.2.3, 9.1.3, 9.0.4, 8.2.9
    • 9.2.1, 9.1.2, 8.2.8, 9.0.3, 8.0.13, 8.1.12
    • Logs, Triggers
    • None

      Issue Summary

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      #None available, it happens randomly in the backend.

      Expected Results

      PlanExec, scheduler and ActiveMQ threads are not blocked

      Actual Results

      Change detection and message handling slows down due to threads being blocked on Java lock.

      Taking a thread dump can show Java deadlock involving ExpirableResettableLazyCloseableReference

      Workaround

      Restart of the application clears the deadlock.

              mgardias Marcin Gardias
              mgardias Marcin Gardias
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: