On Fri, May 7, 2010 at 9:29 AM, jid1jid1 <j...@dharma.gr> wrote: > > Hi, > > I have the following setup: > JMSClient - ActiveMQ 5.3.1 > JMSServer - ActiveMQ 5.3.0 > > I create a QueueConnection-> QueueSession -> MessageConsumer > I set my messageListener on the MessageConsumer and use conn.start() to > flush > > If my queue has messages, When I try to remove the messageListener or even > just CLOSE the connection, I get a deadlock. > > If the queue is empty, everything works as expected. > > Seems like a bug to me. Has anyone experienced this before?
I suggest that you walk through the ActiveMQ examples: http://activemq.apache.org/examples.html Although the examples are very basic, they serve as a very good smoke test to determine if messages are flowing through the broker correctly. I know that these examples work correctly so I'm willing to bet that there is something about your implementation that just needs some fixing. Bruce -- perl -e 'print unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
