Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-6046

Concurrent access to a Transport from WebSocket client can deadlock

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.12.0, 5.12.1, 5.11.3
    • Fix Version/s: 5.13.0
    • Component/s: MQTT, STOMP, Transport
    • Labels:
      None

      Description

      WebSocket connections can encounter a deadlock when the Jetty side allows for concurrent access to the Transport instance that forwards commands onto the broker core. This seems to happen mostly in cases where a message or other action is incoming at the same time as Jetty is closing the connection due to idle timeout or some other cause.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tabish Timothy A. Bish
                Reporter:
                tabish Timothy A. Bish
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: