Hi ,
We are using Active MQ 5.10 version as standalone broker (no cluster).
After few days of run, broker just froze and listeners were not able to
consume messages from the queue. The messages are seen accumulating without
the dequeue count going down.
There are no ResourceAllocation exceptions seen in clients or broker
neither any other exception in AMQ logs. I took a thread dump and could see
a thread in block state :
qtp1472649853-74 Acceptor1 [email protected]:8161" prio=10
tid=0x00007f2a648fa000 nid=0x50c2 waiting for monitor entry
[0x00007f2aede21000]
java.lang.Thread.State: BLOCKED (on object monitor)
at
sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:225)
- waiting to lock <0x00000007003080e0> (a java.lang.Object)
at
org.eclipse.jetty.server.nio.SelectChannelConnector.accept(SelectChannelConnector.java:109)
at
org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:938)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
at java.lang.Thread.run(Thread.java:745)
Can someone please help to let me understand what can be the problem and why
does AMQ just froze without any exceptions being seen at client or server
end. For additional information, I have Flow control on with per destination
policies set.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Active-MQ-5-10-BLOCKED-thread-at-sun-nio-ch-ServerSocketChannelImpl-accept-tp4691008.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
