You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by yolcuabbas <me...@gmail.com> on 2008/02/18 10:36:17 UTC
disabling InactivityMonitor ( maxInactivityDuration = 0 ) disables
failover
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
--
View this message in context: http://www.nabble.com/disabling-InactivityMonitor-%28-maxInactivityDuration-%3D-0-%29-disables-failover-tp15541461s2354p15541461.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: disabling InactivityMonitor ( maxInactivityDuration = 0 )
disables failover
Posted by yolcuabbas <me...@gmail.com>.
thx much.
ragards
yolcuabbas
rajdavies wrote:
>
> 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.
>>
>
>
>
--
View this message in context: http://www.nabble.com/disabling-InactivityMonitor-%28-maxInactivityDuration-%3D-0-%29-disables-failover-tp15541461s2354p15562521.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: disabling InactivityMonitor ( maxInactivityDuration = 0 ) disables failover
Posted by Rob Davies <ra...@gmail.com>.
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.
>
Re: disabling InactivityMonitor ( maxInactivityDuration = 0 )
disables failover
Posted by yolcuabbas <me...@gmail.com>.
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.
Re: disabling InactivityMonitor ( maxInactivityDuration = 0 )
disables failover
Posted by rajdavies <ra...@gmail.com>.
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-tp15541461s2354p15547089.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.