Consuming and producing on the same connection can lead to deadlocks because producer-flow-control blocks the entire connection.
It is hard to tell from the description of the usage pattern if that could be occurring in your case. Sent from my iPhone > On Mar 3, 2014, at 9:55 AM, "jmachina [via ActiveMQ]" > <[email protected]> wrote: > > The majority of our connections have both subscribers and producers, but in > most cases we subscribe to a set of topics, and publish to a different set of > topics (with the same connection). Why are you suggesting that we avoid this, > do you have a longer explanation or a link to docs? Our connections are all > using bare java calls to the ActiveMQ library. Thanks! > > If you reply to this email, your message will be added to the discussion > below: > http://activemq.2283324.n4.nabble.com/Deadlock-on-broker-thread-dumps-included-tp4678423p4678480.html > To start a new topic under ActiveMQ - User, email > [email protected] > To unsubscribe from ActiveMQ - User, click here. > NAML -- View this message in context: http://activemq.2283324.n4.nabble.com/Deadlock-on-broker-thread-dumps-included-tp4678423p4678486.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
