oker URL with this
>> failover:tcp://
>
> :
>
> ,tcp://
>
> :
>
> ?closeAsync=false
>>
>> Hope it helps!
>>
>> Regards,
>> Crishel Yumul
>> DevOps
>> TORO Limited
>>
>>
>>
>> --
>> View this messa
rishel Yumul
> DevOps
> TORO Limited
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Consumer-does-not-reconnect-tp4714039p4714219.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Hi,
configure your broker URL with this
failover:tcp://:,tcp://:?closeAsync=false
Hope it helps!
Regards,
Crishel Yumul
DevOps
TORO Limited
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Consumer-does-not-reconnect-tp4714039p4714219.html
Sent from the ActiveMQ - User
/Consumer-does-not-reconnect-tp4714039p4714084.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
might keep the broken connection in the
consumer rather than replacing it with a new (working) one?
Regards,
Martin
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Consumer-does-not-reconnect-tp4714039p4714084.html
Sent from the ActiveMQ - User mailing list archive at
with a
connection pool since the consumer does not reconnect in any way.
Did somebody already experience a similar behaviour and has a hint?
Thanks already in advance.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Consumer-does-not-reconnect-tp4714039.html
Sent from the
in.
It looks to us like the failover is not working in combination with a
connection pool since the consumer does not reconnect in any way.
Did somebody already experience a similar behaviour and has a hint?
Thanks already in advance.
--
View this message in context:
http://activemq.2283324
