are your producer and consumer share same connection? If yes try to avoid that. I had similar problem. Also if you are using spring jmstemplate read following link.
http://singztechmusings.wordpress.com/2011/06/21/pooledconnectionfactory-vs-cachingconnectionfactory-which-one-is-a-perfect-match-for-spring-jmstemplate/ hope this helps. On Mon, Mar 3, 2014 at 8:24 AM, jmachina <[email protected]>wrote: > The consumers have not been getting blocked up (that we know of), and we > would hope that messages would be discarded for those blocked consumers > rather than block the whole message broker and hang the system. (far > preferable to have one consumer not receive messages than have the whole > system become unresponsive). > > We aren't using a network of brokers. > > We normally operate with ~100 non-temporary topics, and they'll be live > throughout the day. Temporary queues are created on a per-consumer basis > for > synch/asynch request-reply message flows (currently 975 active temporary > queues). > > Anything else I could do to help debug this? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Deadlock-on-broker-thread-dumps-included-tp4678423p4678472.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
