Hi.

We're having a problem under moderate to heavy load (~2500 nonpersisted
messages /second on a single broker) while producers will just hang
indefinitely at some point and producer application needs to be restarted in
order to continue.

Here's a snippet from a producer application thread dump after hang:

at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:317)
        at
org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:40)
        at
org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:80)
        at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1195)
        at
org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1644)
        - locked <0x00002aaab5abeb30> (a java.lang.Object)
        at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:227)
        at
org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:241)
        at
org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:597)

So far we've tried upgrading AMQ from 5.1 to 5.2 and increasing the memory
limits in broker config, both giving no result, the problem still exists.
Neither application nor activemq log displays any errors / exceptions.

One thing i have noticed is that for every message sent to a topic, there
are 2 advisory messages being produced in
ActiveMQ.Advisory.Producer.Topic.TOPICNAME which strikes me as odd but i
haven't been able to find any information in forums or manual about whether
this is normal behaviour?

Producer side is a standalone Spring application with AMQ connectionfactory
wrapped in spring SingleConnectionFactory and used in jmstemplate, as per
example.

Any insight would be greatly appreciated.

Tanel Unt
Core Developer
Tracking Center Ltd.
-- 
View this message in context: 
http://www.nabble.com/Producers-hang-under-load-with-AMQ-5.2-tp25251841p25251841.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to