-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.2.1
-
None
A thread deadlock is occurring within the org.apache.activemq.broker.TransportConnection. The deadlock precludes the creation of additional WebSocket connections. Here's a snapshot of the deadlock taken from attached and scrubbed thread dump:
"qtp1184557276-2796 Selector0" - Thread t@2796 java.lang.Thread.State: BLOCKED at org.apache.activemq.broker.TransportConnection.removeProducerBrokerExchange(TransportConnection.java:1506) - waiting to lock <25c105dc> (a java.util.HashMap) owned by "qtp1184557276-318146" t@318146 at org.apache.activemq.broker.TransportConnection.processRemoveProducer(TransportConnection.java:643) at org.apache.activemq.broker.TransportConnection.processRemoveSession(TransportConnection.java:749) at org.apache.activemq.broker.TransportConnection.processRemoveConnection(TransportConnection.java:854) - locked <4fb667e2> (a org.apache.activemq.broker.jmx.ManagedTransportConnection) "qtp1184557276-318146" - Thread t@318146 java.lang.Thread.State: BLOCKED at org.apache.activemq.broker.TransportConnection.lookupConnectionState(TransportConnection.java:1612) - waiting to lock <4fb667e2> (a org.apache.activemq.broker.jmx.ManagedTransportConnection) owned by "qtp1184557276-2796 Selector0" t@2796 at org.apache.activemq.broker.TransportConnection.getProducerBrokerExchange(TransportConnection.java:1482) - locked <25c105dc> (a java.util.HashMap) at org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:544) at org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:768)
- is related to
-
AMQ-6275 Loading...
