From dev-return-17503-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Fri Nov 06 13:29:24 2009 Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 7685 invoked from network); 6 Nov 2009 13:29:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Nov 2009 13:29:24 -0000 Received: (qmail 13201 invoked by uid 500); 6 Nov 2009 13:29:24 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 13134 invoked by uid 500); 6 Nov 2009 13:29:23 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 13124 invoked by uid 99); 6 Nov 2009 13:29:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 13:29:23 +0000 X-ASF-Spam-Status: No, hits=-1998.5 required=10.0 tests=ALL_TRUSTED,WEIRD_PORT X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 13:29:13 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C9125234C04C for ; Fri, 6 Nov 2009 05:28:52 -0800 (PST) Message-ID: <581809542.1257514132819.JavaMail.jira@brutus> Date: Fri, 6 Nov 2009 05:28:52 -0800 (PST) From: "Gary Tully (JIRA)" To: dev@activemq.apache.org Subject: [jira] Commented: (AMQ-2479) Channel was inactive for too long In-Reply-To: <646731141.1257443332733.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55199#action_55199 ] Gary Tully commented on AMQ-2479: --------------------------------- you need to provide some more info here, like the route descriptions on #1 and #2. In any event, #1 that does a dequeue and enqueue needs to use a dequeue transaction that spans the enqueue such that there is no inflight message loss. Also, in the event of B failure, the failover transport on the jms connection will do an auto reconnect. How are the activemq components configured to access brokers, are the brokers persistent? Again, attaching a test case or some variant of your routes would help. > Channel was inactive for too long > --------------------------------- > > Key: AMQ-2479 > URL: https://issues.apache.org/activemq/browse/AMQ-2479 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.3.0 > Environment: Windows 2003 Server RC2, Enterprise Edition, SP2 > Reporter: Christian A. Kenyeres > Priority: Critical > > We have application #1 that pulls records from a DB, puts them into messages, and sends them to a local queue on server A. That queue routes to a 2nd queue on server B using camel routing. > On Server A, the application log and AMQ log both show the messages being created and persisted in the queue. > On Server B, application #2 pulls, messages from its queue which were routed from the queue on Server A. > From application #2's log, for a 2 minute period of time, ActiveMQ threw this exception: > 14:11:01,317 ERROR [WrapperSimpleAppMain] (application2.java:1072) - Problem creating session... javax.jms.JMSException: Channel was inactive for too long: ServerB.foo.com/10.0.40.138:61616 > and there were also 20 other Exceptions thrown: > 14:12:27,158 ERROR [WrapperSimpleAppMain] (application2.java:1072) - Problem creating session... javax.jms.JMSException: Could not connect to broker URL: tcp://ServerB.foo.com:61616. Reason: java.net.ConnectException: Connection refused: connect > On Server B, application #2's log and the AMQ log have no record of 155 records that were verified as created, put into messages, and sent on Server A. > The application blew up and the wrapper service restarted it. All records & messages before the incident were ok before and after the incident. > The question is, what happened to the messages when the broker crashed on Server B? > Software used: > ActiveMQ 5.3.0 > Camel 2.0.0 > Java JDK 1.6u16 > Java Service Wrapper (tanukisoftware) v 3.3.7 (x86-32) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.