activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ManojC <ma...@castiron.com>
Subject Re: Deadlock in Active MQ 5.0
Date Mon, 07 Jan 2008 21:50:26 GMT

Thanks all for the answers. Updating to the latest snapshot resolved the
issue. 

Thanks
Manoj

JRadecki wrote:
> 
> Just paying it forward... see my post in:
> http://www.nabble.com/-jira--Created%3A-%28AMQ-1490%29-Deadlocks-%28with-JUnit-tests%29-td13702734i20.html#a14605939
> 
> Also, there are quite a few other options for the transports and
> connections, persistence, etc.  Hope the
> above corrects your problem.  My expierence has usally forcused on the
> Journals.  Let me know if this helps...
> 
> 
> 
> 
> ManojC wrote:
>> 
>> ok let me try this and I will let you know once I am able to do that.
>> 
>> rajdavies wrote:
>>> 
>>> This looks like a very old version you are using - could you use the  
>>> latest ActiveMQ snapshot ?
>>> On Jan 5, 2008, at 1:36 AM, ManojC wrote:
>>> 
>>>>
>>>> No we are not running on jre 1.4 it is the one which come with JDK  
>>>> 1.6.
>>>>
>>>> Thanks
>>>> Manoj
>>>>
>>>> ManojC wrote:
>>>>>
>>>>> Did any body faced this problem. My application get stuck on this  
>>>>> stack
>>>>> trace in 5.0. The project was done in such way that it getMessage  
>>>>> from
>>>>> Queue1 and post to Queue2 and the other one getFromthe Queue1 and  
>>>>> post
>>>>> back to Queue2.
>>>>> so it look like something
>>>>>
>>>>> poll(q1)->send)q2)
>>>>> ->poll(q2)->send(q1)
>>>>>
>>>>> Before getting the message from the Queue we browse to see if there 

>>>>> is any
>>>>> message in the queue or not using the QueueBrowser if there is then 

>>>>> we go
>>>>> and fetch the message.
>>>>>
>>>>> When we try to deactivate our application it get stuck on the  
>>>>> following
>>>>> stack
>>>>> ool-5-thread-11" prio=10 tid=0x7f378000 nid=0x1895 in Object.wait()
>>>>> [0x7c984000..0x7c984770]
>>>>>   java.lang.Thread.State: WAITING (on object monitor)
>>>>>        at java.lang.Object.wait(Native Method)
>>>>>        at java.lang.Object.wait(Object.java:485)
>>>>>        at
>>>>> edu 
>>>>> .emory 
>>>>> .mathcs 
>>>>> .backport.java.util.concurrent.locks.CondVar.await(CondVar.java:75)
>>>>>        - locked <0x87861060> (a
>>>>> edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar)
>>>>>        at
>>>>> edu 
>>>>> .emory 
>>>>> .mathcs 
>>>>> .backport 
>>>>> .java 
>>>>> .util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:318)
>>>>>        at
>>>>> org 
>>>>> .apache 
>>>>> .activemq.transport.FutureResponse.getResult(FutureResponse.java:42)
>>>>>        at
>>>>> org 
>>>>> .apache 
>>>>> .activemq 
>>>>> .transport.ResponseCorrelator.request(ResponseCorrelator.java:75)
>>>>>        at
>>>>> org 
>>>>> .apache 
>>>>> .activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:

>>>>> 1171)
>>>>>        at
>>>>> org 
>>>>> .apache 
>>>>> .activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:1660)
>>>>>        at
>>>>> org 
>>>>> .apache 
>>>>> .activemq 
>>>>> .ActiveMQMessageConsumer.<init>(ActiveMQMessageConsumer.java:197)
>>>>>        at
>>>>> org.apache.activemq.ActiveMQQueueBrowser 
>>>>> $1.<init>(ActiveMQQueueBrowser.java:104)
>>>>>        at
>>>>> org 
>>>>> .apache 
>>>>> .activemq 
>>>>> .ActiveMQQueueBrowser.createConsumer(ActiveMQQueueBrowser.java:102)
>>>>>        at
>>>>> org 
>>>>> .apache 
>>>>> .activemq.ActiveMQQueueBrowser.<init>(ActiveMQQueueBrowser.java:88)
>>>>>        at
>>>>> org 
>>>>> .apache.activemq.ActiveMQSession.createBrowser(ActiveMQSession.java:

>>>>> 1116)
>>>>>        at
>>>>> com 
>>>>> .approuter 
>>>>> .module 
>>>>> .jms.activity.MessagePoller.isMessageInQueue(MessagePoller.java:182)
>>>>>        at
>>>>> com 
>>>>> .approuter.module.jms.activity.MessagePoller.run(MessagePoller.java:

>>>>> 103)
>>>>>        at
>>>>> com.approuter.module.common.resource.PollingJob.run(PollingJob.java:

>>>>> 66)
>>>>>        - locked <0x8705de50> (a
>>>>> com.approuter.module.common.resource.PollingJob)
>>>>>        at
>>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java: 
>>>>> 441)
>>>>>        at
>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>        at
>>>>> java.util.concurrent.ScheduledThreadPoolExecutor 
>>>>> $ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
>>>>>        at
>>>>> java.util.concurrent.ScheduledThreadPoolExecutor 
>>>>> $ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
>>>>>        at
>>>>> java.util.concurrent.ThreadPoolExecutor 
>>>>> $Worker.runTask(ThreadPoolExecutor.java:885)
>>>>>        at
>>>>> java.util.concurrent.ThreadPoolExecutor 
>>>>> $Worker.run(ThreadPoolExecutor.java:907)
>>>>>        at java.lang.Thread.run(Thread.java:619)
>>>>>
>>>>>
>>>>> Any idea will appreciated. How can I open a bug against Active MQ 5.0
>>>>>
>>>>>
>>>>>
>>>>
>>>> -- 
>>>> View this message in context:
>>>> http://www.nabble.com/Deadlock-in-Active-MQ-5.0-tp14627978s2354p14628715.html
>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>
>>> 
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Deadlock-in-Active-MQ-5.0-tp14627978s2354p14676911.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message