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

Concurrent access to a MQTT Transport from WebSocket client can deadlock

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.13.3
    • Fix Version/s: 5.13.4, 5.14.0
    • Component/s: Broker
    • Labels:
      None

      Description

      Just like in AMQ-6046, 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 was fixed for Stomp in AMQ-6046 but also needs to be fixed for MQTT.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cshannon Christopher L. Shannon
                Reporter:
                cshannon Christopher L. Shannon
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: