ExpirableResettableLazyCloseableReference can deadlock

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • 9.3.0, 9.2.3, 9.1.3, 9.0.4, 8.2.9
    • Affects Version/s: 9.2.1, 9.1.2, 8.2.8, 9.0.3, 8.0.13, 8.1.12
    • Component/s: Logs, Triggers
    • None
    • 1
    • Severity 2 - Major

      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.

            Assignee:
            Marcin Gardias
            Reporter:
            Marcin Gardias
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: