activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sparky2708 <da...@columbia.edu>
Subject Re: Inactivity monitor exception is closing connection.
Date Fri, 22 Feb 2008 05:45:35 GMT

    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 maxinactivity property. What should
that be set to? (I thought it is set pretty high at 3000ms by default?).
Still not clear if this is a known bug and when would it be resolved? Seems
like a lot of people are seeing this...



Zao Liu wrote:
> 
> 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 <daa82@columbia.edu> 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 [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.197:61616
>> >       at
>> > org.apache.activemq.util.JMSExceptionSupport.create(
>> JMSExceptionSupport.java:49)
>> >       at
>> > org.apache.activemq.ActiveMQConnection.onAsyncException(
>> ActiveMQConnection.java:1649)
>> >       at
>> > org.apache.activemq.ActiveMQConnection.onException(
>> ActiveMQConnection.java:1666)
>> >       at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> >       at
>> > org.apache.activemq.transport.ResponseCorrelator.onException(
>> ResponseCorrelator.java:116)
>> >       at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> >       at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> >       at
>> > org.apache.activemq.transport.WireFormatNegotiator.onException(
>> WireFormatNegotiator.java:143)
>> >       at
>> > org.apache.activemq.transport.InactivityMonitor.onException(
>> InactivityMonitor.java:204)
>> >       at
>> > org.apache.activemq.transport.InactivityMonitor$4.run(
>> InactivityMonitor.java:142)
>> >       at
>> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>> ThreadPoolExecutor.java:650)
>> >       at
>> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
>> ThreadPoolExecutor.java:675)
>> >       at java.lang.Thread.run(Thread.java:595)
>> > Caused by: org.apache.activemq.transport.InactivityIOException: Channel
>> > was inactive for too long: puccell/10.0.55.197:61616
>> >       ... 4 more
>> > 21/02/2008 08:03:35,098 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.197:61616
>> >       at
>> > org.apache.activemq.util.JMSExceptionSupport.create(
>> JMSExceptionSupport.java:49)
>> >       at
>> > org.apache.activemq.ActiveMQConnection.onAsyncException(
>> ActiveMQConnection.java:1649)
>> >       at
>> > org.apache.activemq.ActiveMQConnection.onException(
>> ActiveMQConnection.java:1666)
>> >       at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> >       at
>> > org.apache.activemq.transport.ResponseCorrelator.onException(
>> ResponseCorrelator.java:116)
>> >       at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> >       at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> >       at
>> > org.apache.activemq.transport.WireFormatNegotiator.onException(
>> WireFormatNegotiator.java:143)
>> >       at
>> > org.apache.activemq.transport.InactivityMonitor.onException(
>> InactivityMonitor.java:204)
>> >       at
>> > org.apache.activemq.transport.InactivityMonitor$4.run(
>> InactivityMonitor.java:142)
>> >       at
>> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>> ThreadPoolExecutor.java:650)
>> >       at
>> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
>> ThreadPoolExecutor.java:675)
>> >       at java.lang.Thread.run(Thread.java:595)
>> > Caused by: org.apache.activemq.transport.InactivityIOException: Channel
>> > was inactive for too long: puccell/10.0.55.197:61616
>> >       ... 4 more
>> >
>> > Anybody have a workaround? I am having problems using this version
>> because
>> > it just kicks off all of my services after awhile!
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15622035.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15628176.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message