-
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.
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&wireFormat.maxFrameSize=104857600&needClientAuth=true&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.