You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by skarthik <ka...@necam.com> on 2006/06/22 01:11:38 UTC
Publish call hangs
Hi,
We encountered the following problem on our stress test bed which has one
activeMQ server and a number of JMS Client processes. We are using activeMQ
4.0 with persistent messaging.
Under a lot of stress (large volume of messages and large number of
clients/sessions), the activeMQ client processes (which each have multiple
JMS producer and consumer sessions on a single JMS connection) hang up on
the following call trace. The call never returns, even after few hours. Any
ideas?
"CHRcvr-7" prio=6 tid=0x02f47ca0 nid=0xbb0 in Object.wait()
[0x0bb2f000..0x0bb2fae8]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:474)
at
edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar.await(CondVar.java:75)
- locked <0x242c4500> (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:38)
at
org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:74)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1131)
at
org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1555)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:462)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:384)
at
org.apache.activemq.ActiveMQTopicPublisher.publish(ActiveMQTopicPublisher.java:151)
....
....
regards
karthik
--
View this message in context: http://www.nabble.com/Publish-call-hangs-t1827219.html#a4984398
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Publish call hangs
Posted by James Strachan <ja...@gmail.com>.
On 6/22/06, skarthik <ka...@necam.com> wrote:
>
> I guessed so. Would enabling asyncSend then, avoid this problem? As our
> application is written to tolerate occasional loss of messages.
Absolutely; if you don't mind about blocking synchronously until you
know the message definitely got to the broker (or broker's disk for
persistent messaging) then definitely use async sends as its *much*
faster and avoids your client blocking waiting for receipts from the
broker
--
James
-------
http://radio.weblogs.com/0112098/
Re: Publish call hangs
Posted by skarthik <ka...@necam.com>.
I guessed so. Would enabling asyncSend then, avoid this problem? As our
application is written to tolerate occasional loss of messages.
-karthik
--
View this message in context: http://www.nabble.com/Publish-call-hangs-t1827219.html#a4994112
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Publish call hangs
Posted by James Strachan <ja...@gmail.com>.
It looks like they are just waiting for the receipt back from the
broker after its persisted the messages to disk etc
On 6/22/06, skarthik <ka...@necam.com> wrote:
>
> Hi,
>
> We encountered the following problem on our stress test bed which has one
> activeMQ server and a number of JMS Client processes. We are using activeMQ
> 4.0 with persistent messaging.
>
> Under a lot of stress (large volume of messages and large number of
> clients/sessions), the activeMQ client processes (which each have multiple
> JMS producer and consumer sessions on a single JMS connection) hang up on
> the following call trace. The call never returns, even after few hours. Any
> ideas?
>
>
> "CHRcvr-7" prio=6 tid=0x02f47ca0 nid=0xbb0 in Object.wait()
> [0x0bb2f000..0x0bb2fae8]
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:474)
> at
> edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar.await(CondVar.java:75)
> - locked <0x242c4500> (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:38)
> at
> org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:74)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1131)
> at
> org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1555)
> at
> org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:462)
> at
> org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:384)
> at
> org.apache.activemq.ActiveMQTopicPublisher.publish(ActiveMQTopicPublisher.java:151)
> ....
> ....
>
> regards
> karthik
> --
> View this message in context: http://www.nabble.com/Publish-call-hangs-t1827219.html#a4984398
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/