activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Hanik - Dev Lists <>
Subject Re: Need Help with blocking Producer!
Date Fri, 09 May 2008 05:08:33 GMT
that means youre producing messages faster than they are being consumed.

you could setup a policy entry to turn off flow control

<policyEntry topic="topicname" producerFlowControl="false" 

<policyEntry queue="queuename" producerFlowControl="false" 

however, if your consumers never catch up, then you need to decide what 
you wanna do with your messages, as eventually you will run out of 
resources, being it memory or disk space that holds all the messages.

the <policyEntry> element has a bunch of sub element that you can setup 
to control other needs


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(
> 	- waiting to lock <0x07c45ea0> (a java.lang.Object)
> 	at
> org.apache.activemq.ActiveMQMessageProducer.send(
> 	at
> org.apache.activemq.ActiveMQMessageProducerSupport.send(
> 	at
> org.apache.activemq.ActiveMQTopicPublisher.publish(
> The connection URI looks like the following
> failover:(tcp://
> 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 raw message