there's
>>> a cleaner way to make this work reliably? Especially in the case
>>> where the
>>> first connection attempt would hang, and thus can't even initialize
>>> the
>>> TransportListener, etc
>>>
>>> I'm using
;> I'm using AMQ 4.1.1, by the way, with Jencks AMQPool....I've
>> modified the
>> ActiveMQConnectionFactory to use a setTransportListener method
>> (basically
>> copied the same model as was done for AMQ 5.X)
>>
>> Finally, what is the reason f
e self-recovering if a broker becomes available?
Jason
What approaches have others tried?
--
View this message in context: http://www.nabble.com/How-to-use-
TransportListener-with-FailoverTransport-tf4824542s2354.html#a13803554
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
omes available?
Jason
What approaches have others tried?
--
View this message in context:
http://www.nabble.com/How-to-use-TransportListener-with-FailoverTransport-tf4824542s2354.html#a13803554
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
