Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 32147 invoked from network); 28 Apr 2010 12:49:11 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Apr 2010 12:49:11 -0000 Received: (qmail 8377 invoked by uid 500); 28 Apr 2010 12:49:11 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 8258 invoked by uid 500); 28 Apr 2010 12:49:10 -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 8245 invoked by uid 99); 28 Apr 2010 12:49:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Apr 2010 12:49:10 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.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; Wed, 28 Apr 2010 12:49:04 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1O76h1-00024a-7V for users@activemq.apache.org; Wed, 28 Apr 2010 05:48:43 -0700 Message-ID: <28387759.post@talk.nabble.com> Date: Wed, 28 Apr 2010 05:48:43 -0700 (PDT) From: sids To: users@activemq.apache.org Subject: EOFException and Channel was inactive for too long MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: siddharthans@ymail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, We have developed an application which uses Apache Active MQ v5.3.0. We are currently Load Testing the application. We are getting the "javax.jms.JMSException: Channel was inactive for too long:" exception and the javax.jms.JMSException: java.io.EOFException. The higher the load, the faster we get these Exceptions. For example, for a medium load, these Exceptions were thrown after 32 hours from the start of test. For a high load, we got this error in just 2.5 hours. We have set maxInactivityDuration=300000 (5 minutes) and made keepAlive=true. A bug has already been logged which is similar to the issue we are facing - https://issues.apache.org/activemq/browse/AMQ-2067 If there is any work-around for this issue, please let me know. Thanks, Sid. -- View this message in context: http://old.nabble.com/EOFException-and-Channel-was-inactive-for-too-long-tp28387759p28387759.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.