ple where those log lines is important to
> diagnose - when a broker is running out of memory (usually due to a
> slow-consumer problem).
--
View this message in context:
http://activemq.2283324.n4.nabble.com/when-should-you-set-maxInactivityDuration-0-tp4688281p4688572.html
Sent from the Ac
Thanks!
I think I'll leave everything as it is. Given what's going on with this
particular network environment, I'd wager it was a hiccup. I haven't seen this
error since then.
Steve
Good point Tim. One example where those log lines is important to diagnose -
when a broker is running out of memory (usually due to a slow-consumer
problem).
--
View this message in context:
http://activemq.2283324.n4.nabble.com/when-should-you-set-maxInactivityDuration-0-tp4688281p4688291
once a
long time ago, I wouldn't worry about it -- once in a blue moon is probably
just a network hiccup, and you only need to worry about it when it becomes
a pattern.
Tim
On Tue, Dec 2, 2014 at 12:49 PM, artnaseef wrote:
> Setting maxInactivityDuration to 0 disables the activity mon
Setting maxInactivityDuration to 0 disables the activity monitor. The
advantages include reducing the overhead when there are large numbers of
idle connections, and eliminating forced disconnects on slow connections
that are otherwise active.
These seem like minor advantages. The overhead is
Some time ago I noticed a dropped connection, and saw an error along the lines
of "Channel was inactive for too long". I made note of various folks here and
elsewhere saying that the way to prevent this from happening is adding
wireFormat.maxInactivityDuration=0
So now I've got the time to lo
Mohit,
The clients will take that parameter and used it to monitor connections.
On 01/02/13 21:58, Mohit Anchlia wrote:
If I set maxInactivityDuration to 0 on server and leave clients with some
value then which overrides? Would server override client in this case?
--
Andreas Calvo Gómez
Without looking at NMS, the statement you quote *isn't generally true* for
the purposes of keepalive packets being sent.
The first sentence is false: it doesn't need to match, ditto the 2nd and
3rd.
"When using the maxInactivityDuration option, the setting must match on bo
On Wed, 2010-11-03 at 19:09 +0100, Oscar Pernas wrote:
> Hi all,
>
> I've read something about the maxinactivityduration to prevent the closing
> of producers/consumers while I'am debugging. I've tried to set in the url
> like this:
>
> ?maxInactivityDuration
Hi all,
I've read something about the maxinactivityduration to prevent the closing
of producers/consumers while I'am debugging. I've tried to set in the url
like this:
?maxInactivityDuration=0
But I have still seeing that the channel is being closed, What Im doing
wrong?
--
Óscar Pernas Plaza.
, 2009-04-08 at 18:58 -0700, polygraph wrote:
>> >> I have fixed the bug in activemq-cpp.
>> >>
>> >>
>> > Care to share? How about opening a Jira issue and attaching a patch?
>> >
>> > Regards
>> > Tim.
>> >
>
> > Tim.
> >
> >
> >>
> >> polygraph wrote:
> >> >
> >> > I checked all the code in ActiveMQ-CPP 2.2.5 , I think
> >> > maxInactivityDuration of Wire-Format is not supported in the code.
> >> > I had want to co
a patch?
>
> Regards
> Tim.
>
>
>>
>> polygraph wrote:
>> >
>> > I checked all the code in ActiveMQ-CPP 2.2.5 , I think
>> > maxInactivityDuration of Wire-Format is not supported in the code.
>> > I had want to configure the
On Wed, 2009-04-08 at 18:58 -0700, polygraph wrote:
> I have fixed the bug in activemq-cpp.
>
>
Care to share? How about opening a Jira issue and attaching a patch?
Regards
Tim.
>
> polygraph wrote:
> >
> > I checked all the code in ActiveMQ-CPP 2.2.5 , I think
&
I have fixed the bug in activemq-cpp.
polygraph wrote:
>
> I checked all the code in ActiveMQ-CPP 2.2.5 , I think
> maxInactivityDuration of Wire-Format is not supported in the code.
> I had want to configure the Parameter to kill some died connections.
>
> I do not kno
I checked all the code in ActiveMQ-CPP 2.2.5 , I think maxInactivityDuration
of Wire-Format is not supported in the code.
I had want to configure the Parameter to kill some died connections.
I do not know why the argument is not supported in ActiveMQ-CPP or there is
other way to kill the died
Env: Jre 1.6,
ActiveMQ 4.1.1
Linux
I have a couple of applications connecting to a single external broker
using TCP transport.
(app1) <> External Broker <=> (app2)
If I have maxInactivityDuration configured to 0 (inactivity monitor disabled),
as
t;>
>>>
>>>
>>> yolcuabbas wrote:
>>>>
>>>> Hi,
>>>>
>>>> we use activemq 4.1.1 and have following problem. the uri is
>>>> failover://(tcp://:xxx?wireFormat.maxInactivityDuration=0).
>>>>
, 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://:xxx?wireFormat.maxInactivityDuration=0).
If I put the value of maxInactivityDuration to 0 and try to
emq 4.1.1 and have following problem. the uri is
>> failover://(tcp://: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
>>
yolcuabbas wrote:
>
> Hi,
>
> we use activemq 4.1.1 and have following problem. the uri is
> failover://(tcp://:xxx?wireFormat.maxInactivityDuration=0).
>
> If I put the value of maxInactivityDuration to 0 and try to stop the
> connection over jconsole, my client
Hi,
we use activemq 4.1.1 and have following problem. the uri is
failover://(tcp://: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
22 matches
Mail list logo
