Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 20034 invoked from network); 21 Feb 2008 22:52:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Feb 2008 22:52:45 -0000 Received: (qmail 32759 invoked by uid 500); 21 Feb 2008 22:52:40 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 32560 invoked by uid 500); 21 Feb 2008 22:52:39 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 32551 invoked by uid 99); 21 Feb 2008 22:52:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Feb 2008 14:52:39 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Feb 2008 22:52:05 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JSKGy-0006oy-31 for users@activemq.apache.org; Thu, 21 Feb 2008 14:52:12 -0800 Message-ID: <15622035.post@talk.nabble.com> Date: Thu, 21 Feb 2008 14:52:10 -0800 (PST) From: sparky2708 To: users@activemq.apache.org Subject: Re: Inactivity monitor exception is closing connection. In-Reply-To: <15611505.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: daa82@columbia.edu References: <15404620.post@talk.nabble.com> <15611505.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org 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.