Just wanted to add that we are using Durable Topic Subscribers with Persistent delivery mode. Also the number of messages published is not very many. A few hundred messages. The producers are also consumers of the message and a single connection is being used for publish and subscribe.
Any help appreciated! jaya_srini wrote: > > hi > > We are using ActiveMQ 5.0 release and observing the following on > production. After a certain number of messages are sent the Activemq send > blocks. The thread dump produced the following > > daemon prio=6 tid=0x3793f400 nid=0x1f28 waiting for monitor entry > [0x38aff000..0x38affc98] > java.lang.Thread.State: BLOCKED (on object monitor) > at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1587) > - waiting to lock <0x07c45ea0> (a java.lang.Object) > at > org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:226) > at > org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:268) > at > org.apache.activemq.ActiveMQTopicPublisher.publish(ActiveMQTopicPublisher.java:146) > > > The connection URI looks like the following > > failover:(tcp://10.11.12.13:61616?wireFormat.maxInactivityDuration=-1) > > I am not sure if jms.useAsyncSend=true or jms.dispatchAsync=true will work > with a failover transport. > > Can someone please help me troubleshoot this? Will increasing the memory > limit on the broker help? > > -- View this message in context: http://www.nabble.com/Need-Help-with-blocking-Producer%21-tp17141146s2354p17141293.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
