Step #2 looks like your problem, based on that thread dump. Are you publishing back to the same broker, or another one? Whichever one it is, is it just overloaded trying to accept 40000 messages all at once? Are those messages actually getting to that broker, and at what rate?
Why is a producer window being used? To what end? Tim On Oct 15, 2015 6:54 AM, "dhananjay.patkar" <dhananjay.pat...@gmail.com> wrote: > No, the broker logs are clear and I dont see any warnings in broker logs. > *I am worried as, even broker resources are within limit this waiting > thread > never returns causing this consumer to die*. > > My workflow is > > Queue -> Camel route jms consumer (uses connectionfactory without > producer window size as its consumer) > 1. Bean Processor to split the > message into multiple (~40k) messages > 2. Send ~40k messages using spring > jmstemplate (uses connectionfactory with producer window) > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-consumer-count-is-set-to-0-tp4675930p4702980.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
