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
13 matches
Mail list logo
