Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of rajdavies@gmail.com
 designates 66.249.92.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
        b=TR+754A6uuRfouRlw+Vv5X6irGZl341waPWg7oeiB/MiF+NnPQPYtXm3zmGOdUS1xFjGILCugEUgi9CsSpaFigK+S2uMWyFFxPq3tkGLMdUGcyVD7XaGz14pcqvAACb3dyXnOE06kNg9WEugmTv3mWgpRwymotRptNj9uYEgPm4=
Message-Id: <E19401F1-AE09-43F6-A3FA-7FE27BB5EDD0@gmail.com>
From: Rob Davies <rajdavies@gmail.com>
To: users@activemq.apache.org
In-Reply-To: <14628715.post@talk.nabble.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: Deadlock in Active MQ 5.0
Date: Sat, 5 Jan 2008 07:23:42 +0000
References: <14627978.post@talk.nabble.com> <14628715.post@talk.nabble.com>

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.
>