In other words, if the asynchronous listener is listening "forever", is it possible to neatly stop that listener by closing the connection, the session, the consumer, etc?
--mrh mrh wrote: > > Thank you for the reply, Tim. > > Yes, this is my primary question: > > > tabish121 wrote: >> >> make that it >> doesn't wait forever for messages and it stops as soon as it gets all >> the messages we told it to. >> > > I would like for it to listen continuously for messages: no countdown, no > wait... just listen in the background while allowing the user to do other > things, until the user wants to exit the entire application. Is the only > way to do this with threads? > > Thanks again, > mrh > > > > On Fri, 2007-10-26 at 06:49 -0700, mrh wrote: >> In the activemq-cpp example code, there is a countdown "latch". If I >> understand it correctly, you can pass in a number of milliseconds that it >> is >> to wait for a message or a number that it will count down to as messages >> are >> received. With this structure, is it possible to asychronously receive >> messages (using the onMessage function to process them) but stop the >> listener from the outside? Say, from an outside thread? >> >> Thanks, >> mrh > > -- View this message in context: http://www.nabble.com/Stop-Thread---Stop-Listening-tf4693571s2354.html#a13428693 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
