n.send(ActiveMQSession.java:1587)
>>>>>- waiting to lock <0x07c45ea0> (a java.lang.Object)
>>>>>at
>>>>> org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:226)
>>>>>at
>>>>> or
.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:226)
>>>>at
>>>> org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:268)
>>>>at
>>>> org.apache.activemq.ActiveMQTopicPublishe
aah, I see, the issue you are running into is a global lock on the session,
only one message can be sent at a time on the same session.
so if you have multiple threads using the same session, it will send the
requests, one at a time
you are probably sending messages synchronously, as opposed to
ctivityDuration=-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-tp17141146s2354p17141951.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
that means youre producing messages faster than they are being consumed.
you could setup a policy entry to turn off flow control
memoryLimit="10mb"/>
memoryLimit="10mb"/>
however, if your consumers never catch up, then you need to decide what
you wanna do with your messages, as eventually y
bleshoot 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.
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-Produ
