Hi,, Did you find any solution to the issue mentioned? Kindly let me know if
you have.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
On Mon, Apr 2, 2018 at 10:35 PM, Rajesh Malla wrote:
> 1) consumer -> broker - inactivity monitor closing connections ?
> for this connection loss we will apply patch which you provided http
> broken. this answer we got.
>
OK, perfect.
> 2) while configuring n/w connector do we need to
1) consumer -> broker - inactivity monitor closing connections ?
for this connection loss we will apply patch which you provided http
broken. this answer we got.
2) while configuring n/w connector do we need to provide any inactivity
parameters ? because I
have not provided due to tha
On Mon, Apr 2, 2018, 11:01 AM Rajesh Malla wrote:
> hello
>
> thank you for the link on inactivity monitor, we will apply that patch and
> we will verify.
>
> I have attached link also https://pastebin.com/M9u7TJZB from this I
> understand that network connector is not closing connection b/w ho
hello
thank you for the link on inactivity monitor, we will apply that patch and
we will verify.
I have attached link also https://pastebin.com/M9u7TJZB from this I
understand that network connector is not closing connection b/w host1 &
host2.
do we need to provide specific parameters while cre
On Sun, Apr 1, 2018, 11:05 PM Rajesh Malla wrote:
> Thank you, actually we searched but not found any bug fix on inactivity
> monitor. there is only one bug which is
> https://issues.apache.org/jira/browse/AMQ-6877 on http connector with
> queue
> prefetch 0. this we applied and queue-prefetch is
Thank you, actually we searched but not found any bug fix on inactivity
monitor. there is only one bug which is
https://issues.apache.org/jira/browse/AMQ-6877 on http connector with queue
prefetch 0. this we applied and queue-prefetch is working fine.
can you please help us. because in our case in
If using HTTP transport then I recall there might have been a bug fixed
for the inactivity and lack of ping commands getting marshaled. That
would probably mean you need to upgrade to a later release though.
Otherwise you'd need to analyze the network traffic and see if a
firewall or somethin
side.
"xbhanu
[via ActiveMQ]" <ml-node+s2283324n4675926...@n4.nabble.com>
01/02/2014 05:17 PM
To
Prashant
Kumar41/India/IBM@IBMIN,
cc
Subject
Re:
Inactivity Monitor
So, I were to increase it this would require me to specify
maxInactivityDuration at bro
So, I were to increase it this would require me to specify
maxInactivityDuration at broker side as well as client side? I mean If I
specify a value say 120 seconds on broker side and do not specify anything
on the client side while connecting to broker, will that make the
configuration to 120 secon
that would disable it, by the same logic that calculates the minimum
both ends would see 0 and disable.
On 18 October 2013 08:05, Prashant wrote:
> If we disable Inactivity Monitor from broker side by adding
> maxInactivityMonitor=0 parameter in broker's transport connector URL but it
> is enable
http://issues.apache.org/activemq/browse/CAMEL-1751
Disregard this section. It was a double paste ..
> class="com.inwk.jobtemplate.server.ReturnedQueueRouteBuilder"
> lazy-init="false" init-method="init" destroy-method="stop">
>
>
>
> class="com.inwk.jobtemplate.server.ReturnedQuotesProce
On Tue, Jun 23, 2009 at 8:34 AM, David Durham wrote:
> On Tue, Jun 23, 2009 at 4:35 AM, Gary Tully wrote:
>> I wonder if this is the result of code registered with a shutdown hook and
>> at shutdown some of the required classes are not longer available.
>> One way to check is to have the broker not
On Tue, Jun 23, 2009 at 4:35 AM, Gary Tully wrote:
> I wonder if this is the result of code registered with a shutdown hook and
> at shutdown some of the required classes are not longer available.
> One way to check is to have the broker not register any shutdown hook.
>
> Set the 'useShutdownHook'
I wonder if this is the result of code registered with a shutdown hook and
at shutdown some of the required classes are not longer available.
One way to check is to have the broker not register any shutdown hook.
Set the 'useShutdownHook' property to false for the ActiveMQ broker in your
xml confi
>> I've got a simple ActiveMQ client running inside Tomcat. When I
>> shutdown Tomcat I get an exception from the "Inactivity Monitor Write
>> Check" thread. My question is has anyone seen this issue and have a
>> fix for it? I've tried making sure that I call the stop() method on
>> my CamelCon
On Mon, Jun 22, 2009 at 2:40 PM, David Durham wrote:
> Hi all,
>
> I've got a simple ActiveMQ client running inside Tomcat. When I
> shutdown Tomcat I get an exception from the "Inactivity Monitor Write
> Check" thread. My question is has anyone seen this issue and have a
> fix for it? I've trie
I also met this situation,and I set a exception listener,when the
exception listener listened this kind of exception.it will redo the sub.
And i also tried setting the maxIn..=0.but it has a bug,i reported it
long time ago.
lurker wrote:
>
> I'm programming some kind of messaging prog
Is this still planned? Does anyone have an idea when it may happen?
rajdavies wrote:
>
>
> [] We should be coming out with a 5.0.1
> real soon that will include the fix
>
>
>
>
--
View this message in context:
http://www.nabble.com/Inactivity-monitor-exception-is-closing-connecti
On 28 Feb 2008, at 09:42, cedricb wrote:
Hi Rob,
We've got the same issue with a Spring 2.5.1/ActiveMQ 5.0.0
application.
I've just tested the apache-activemq-5.1-20080227.125551-32 version
and it
look like the problem is fixed... :-)
When do you think, 5.1 will be release? I don't r
Hi Rob,
We've got the same issue with a Spring 2.5.1/ActiveMQ 5.0.0 application.
I've just tested the apache-activemq-5.1-20080227.125551-32 version and it
look like the problem is fixed... :-)
When do you think, 5.1 will be release? I don't really want to go to
production with a snapshot vers
Would love to know how to do that. Can you give me an example of a test case
or where I would find out how to write a test case?
rajdavies wrote:
>
> Could you please provide a test case ?
>
> cheers,
>
> Rob
> On 21 Feb 2008, at 22:52, sparky2708 wrote:
>
>>
>> This started happening since
Could you please provide a test case ?
cheers,
Rob
On 21 Feb 2008, at 22:52, sparky2708 wrote:
This started happening since we upgraded from 4.1.0. 4.1.0 doesn't
seem to
have this problem.
sparky2708 wrote:
I am getting the same error with SNAPSHOT-5.1:
21/02/2008 08:03:34,335 ERROR [
Reading the forums, doesn't this error mean that there is some problem
with the heartbeat. The client was still alive when it happened as seen in
the previous posts (it did throw the exception when the InactivityMonitor
killed the connection).
I assume you are referring to the maxinactivi
I guess it is a warning for disconnect the clients which has been inactive
for a long time. You can set the time for inactive connection by set
activitymonitor.
On Thu, Feb 21, 2008 at 2:52 PM, sparky2708 <[EMAIL PROTECTED]> wrote:
>
> This started happening since we upgraded from 4.1.0. 4.1.0 d
This started happening since we upgraded from 4.1.0. 4.1.0 doesn't seem to
have this problem.
sparky2708 wrote:
>
> I am getting the same error with SNAPSHOT-5.1:
>
> 21/02/2008 08:03:34,335 ERROR [ActiveMQ Connection Worker:
> tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
> com
I am getting the same error with SNAPSHOT-5.1:
21/02/2008 08:03:34,335 ERROR [ActiveMQ Connection Worker:
tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
com.company_name.messaging.MessageManager::onException
javax.jms.JMSException: Channel was inactive for too long:
puccell/10.0.55.
I am using activemq-all-5.1-SNAPSHOT.jar and still get this error:
2008-02-19 11:44:25,768 (ActiveMQConnection.java:1453) WARN
org.apache.activemq.ActiveMQConnection - Async exception with no exception
listener: org.apache.activemq.transport.InactivityIOException: Channel was
inactive for too lo
Thanks for your fast reply, Rob.
I tried activeMQ 5.1.
The connection alive time is longer than 5.0 version that I used before.
But it still closes the connection after some while.
I attach the exception logs below.
Is there any configuration value for idle timeout?
-
18:34:04,249 DEBUG [In
Could you try a snaphot of ActiveMQ 5.1 ?
thanks,
Rob
On Feb 11, 2008, at 2:40 AM, lurker wrote:
I'm programming some kind of messaging program that sends messages
in sparse
frequency using activeMQ.
I got exceptions like following and connection between client and
activeMQ
server is c
31 matches
Mail list logo
