activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Davies <rajdav...@gmail.com>
Subject Re: disabling InactivityMonitor ( maxInactivityDuration = 0 ) disables failover
Date Tue, 19 Feb 2008 08:02:26 GMT
failover depends on the InactivityMonitor - but also socket death too  
- which might take a while to percolate through.

cheers,

Rob
On 19 Feb 2008, at 07:27, yolcuabbas wrote:

>
> Hi,
>
> thanks for prompt reply. We can not upgrade easyl, because we use  
> amq 4.1.1
> in production :( is it true, that failover protocol depends on
> InactivityMonitor?
>
> regards,
> fatih
>
>
> rajdavies wrote:
>>
>>
>>
>> yolcuabbas wrote:
>>>
>>> Hi,
>>>
>>> we use activemq 4.1.1 and have following problem. the uri is
>>> failover://(tcp://xxxx:xxx?wireFormat.maxInactivityDuration=0).
>>>
>>> If I put the value of maxInactivityDuration to 0 and try to stop the
>>> connection over jconsole, my client dont try to reconnect to  
>>> broker. is
>>> the failover protocol depends on inactivityMonitor?
>>>
>>> regards
>>>
>>>
>>
>> Is it possible to move to 5.0 ?
>>
>
> -- 
> View this message in context: http://www.nabble.com/disabling-InactivityMonitor-%28-maxInactivityDuration-%3D-0-%29-disables-failover-tp15541461s2354p15559973.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


Mime
View raw message