, 2010 at 8:45 AM, John Peter wrote:
>>>>
>>>> Hi Guys,
>>>>
>>>> We use TransportListener for Broker Up/Down Status detection and around
>>>> 20
>>>> ActiveMQ Broker statuses need to be continuously monitored.
gt;>>
>>> 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
>>&g
> Blog - http://www.nighttale.net
>>
>>
>>
>> On Mon, Aug 16, 2010 at 8:45 AM, John Peter wrote:
>>>
>>> Hi Guys,
>>>
>>> We use TransportListener for Broker Up/Down Status detection and around
>>> 20
>>> ActiveMQ Brok
> 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 ca
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 Tr
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.