Hi John, TransportListener doesn't monitor if broker is going up and down, but monitors the status of your client's connection. It's set on the connection and it only provides a mechanism for the connection to notify your application on the events. It doesn't require any separate thread or context.
Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Mon, Aug 16, 2010 at 8:45 AM, John Peter <mrth...@yahoo.com> wrote: > > Hi Guys, > > We use TransportListener for Broker Up/Down Status detection and around 20 > ActiveMQ Broker statuses need to be continuously monitored. Since network is > non reliable, we receive the transportInterupted/ transportResumed are being > called very frequently > > My Question is > 1) is TransportListener callback class running in separate Thread ? and > Which Context? > > Thanks and Regards, > John Peter. > -- > View this message in context: > http://old.nabble.com/TransportListener-callback-tp29447156p29447156.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
