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

wss connections not being closed on ActiveMQ side

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 5.14.0
    • Fix Version/s: None
    • Component/s: Transport
    • Labels:
      None
    • Environment:

      Debian (SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux) on AWS, 4 cores, 7.5GB.

      Description

      We have clients that connect via wss to our ActiveMQ.

      Under some circumstances, we have socket connections that appear in the ActiveMQ web console, but when doing a netstat -an we can see that they are not open in the system.

      This means that ActiveMQ is enqueuing messages for that connections, but they are not there.

      This is the transport configuration:

      <transportConnector name="wss" uri="wss://0.0.0.0:8082?maximumConnections=5000&amp;wireFormat.maxFrameSize=104857600&amp;needClientAuth=true&amp;transport.enabledProtocols=TLSv1,TLSv1.1,TLSv1.2" allowLinkStealing="true" enableStatusMonitor="true" />
      

      Is there a way of closing these connections? Is this an error solved in a newer release (could not find it in the release notes)? We have the enableStatusMonitor="true" option, but still the connection is not being closed on the ActiveMQ side. What we need to do right now is restarting ActiveMQ, but it is not desired.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              marcos.moreno Marcos Moreno Martin
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: