Deadlock in ActiveMQ version 4.1

[Martin Joseph <MA...@AA.COM>]

We are using ActiveMQ verions 4.1 and we are facing deadlock situations.  Is
there any way we can apply some patch to the code to fix this issue in
Version 4.1 .  We cannot use the latest version of ActiveMQ as we are in
currently jdk 1.4

Here is the thread dump :

"userAnchorEventsJmsMessageListener-1" prio=5 tid=0x00cedb40 nid=0xa8
runnable [0x9ef81000..0x9ef819c8]
	at java.lang.Object.wait(Native Method)
	at
org.apache.activemq.MessageDispatchChannel.dequeue(MessageDispatchChannel.java:80)
	- locked <0xbc0ce5e0> (a java.lang.Object)
	at
org.apache.activemq.ActiveMQMessageConsumer.dequeue(ActiveMQMessageConsumer.java:377)
	at
org.apache.activemq.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:481)
	at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveMessage(AbstractPollingMessageListenerContainer.java:375)
	at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:300)
	at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:254)
	at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:870)
	at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:810)
	at java.lang.Thread.run(Thread.java:534)
-- 
View this message in context: http://www.nabble.com/Deadlock-in-ActiveMQ-version-4.1-tp18778472p18778472.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Deadlock in ActiveMQ version 4.1

[mostlypeaceful <aa...@mac.com>]

I have the exact same issue with the same thread stack dump.  This appears to
occur after approximately 5000 messages go through our application.  The
application consists of a broker and two groups of listeners threads
(different VM's).  The listener groups will block for up to 5 minutes, and
then one or two threads will become active again.  The normal number of
active threads per group is 25 however.

I know upgrading to 4.1.2 (currently using 4.1.1) or 5.x may fix this issue,
but I'm not in a position to change out our software stack midstream.  Any
help would be greatly appreciated.


Martin Joseph wrote:
> 
> We are using ActiveMQ verions 4.1 and we are facing deadlock situations. 
> Is there any way we can apply some patch to the code to fix this issue in
> Version 4.1 .  We cannot use the latest version of ActiveMQ as we are in
> currently jdk 1.4
> 
> Here is the thread dump :
> 
> "userAnchorEventsJmsMessageListener-1" prio=5 tid=0x00cedb40 nid=0xa8
> runnable [0x9ef81000..0x9ef819c8]
> 	at java.lang.Object.wait(Native Method)
> 	at
> org.apache.activemq.MessageDispatchChannel.dequeue(MessageDispatchChannel.java:80)
> 	- locked <0xbc0ce5e0> (a java.lang.Object)
> 	at
> org.apache.activemq.ActiveMQMessageConsumer.dequeue(ActiveMQMessageConsumer.java:377)
> 	at
> org.apache.activemq.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:481)
> 	at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveMessage(AbstractPollingMessageListenerContainer.java:375)
> 	at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:300)
> 	at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:254)
> 	at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:870)
> 	at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:810)
> 	at java.lang.Thread.run(Thread.java:534)
> 

-- 
View this message in context: http://www.nabble.com/Deadlock-in-ActiveMQ-version-4.1-tp18778472p19191651.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.