From dev-return-31118-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Tue Apr 17 10:53:43 2012 Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3B9769174 for ; Tue, 17 Apr 2012 10:53:43 +0000 (UTC) Received: (qmail 78277 invoked by uid 500); 17 Apr 2012 10:53:43 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 78245 invoked by uid 500); 17 Apr 2012 10:53:43 -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 78234 invoked by uid 99); 17 Apr 2012 10:53:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 10:53:42 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 10:53:37 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 3676639E3C7 for ; Tue, 17 Apr 2012 10:53:16 +0000 (UTC) Date: Tue, 17 Apr 2012 10:53:16 +0000 (UTC) From: "Bhanu (Created) (JIRA)" To: dev@activemq.apache.org Message-ID: <406451935.32404.1334659996243.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (AMQ-3809) Simple ActiveMQ consumer dies on failover MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Simple ActiveMQ consumer dies on failover ----------------------------------------- Key: AMQ-3809 URL: https://issues.apache.org/jira/browse/AMQ-3809 Project: ActiveMQ Issue Type: Bug Components: Broker, Transport Affects Versions: 5.5.1 Environment: solaris, linux Reporter: Bhanu I have a simple consumer application which connects to the broker using failover url. The consumer uses Message listener to asynchronously listen to messages. Whenever i kill my primary broker, I get an EOF exception(which is expected), the consumer tries to connect to failover broker but before it could finish the reconnect, it shuts down. My simple producer connecting with the same failover url never dies and successfully connects to failover broker. What is going on here? Posting the snippet with which the consumer dies:- 2012-04-17 06:45:25,771 WARN org.apache.activemq.transport.failover.FailoverTransport - Transport (host1/10.240.170.28:61616) failed to tcp://host1:61616 , attempting to automatically reconnect due to: java.io.EOFException 2012-04-17 06:45:25,772 DEBUG org.apache.activemq.transport.failover.FailoverTransport - Transport failed with the following exception: java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:392) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:269) at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:227) at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:219) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:202) at java.lang.Thread.run(Thread.java:722) 2012-04-17 06:45:25,774 DEBUG org.apache.activemq.transport.failover.FailoverTransport - urlList connectionList:[tcp://host2:61616, tcp://host1:61616], from: [tcp://host1:61616, tcp://host2:61616] 2012-04-17 06:45:25,774 DEBUG org.apache.activemq.transport.failover.FailoverTransport - Attempting connect to: tcp://host2:61616 [20120417 06:45:25.776 EDT (Shutdown-ActiveMQConsumer) ActiveMQConsumer#stop INFO] Stopping the consumer... 2012-04-17 06:45:26,242 DEBUG org.apache.activemq.transport.failover.FailoverTransport - Stopped. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira