Return-Path: Delivered-To: apmail-geronimo-activemq-dev-archive@www.apache.org Received: (qmail 9258 invoked from network); 8 Jun 2006 18:10:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Jun 2006 18:10:57 -0000 Received: (qmail 76159 invoked by uid 500); 8 Jun 2006 18:10:56 -0000 Delivered-To: apmail-geronimo-activemq-dev-archive@geronimo.apache.org Received: (qmail 76129 invoked by uid 500); 8 Jun 2006 18:10:56 -0000 Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-dev@geronimo.apache.org Delivered-To: mailing list activemq-dev@geronimo.apache.org Received: (qmail 76116 invoked by uid 99); 8 Jun 2006 18:10:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jun 2006 11:10:56 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jun 2006 11:10:55 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 984A07142CC for ; Thu, 8 Jun 2006 18:09:51 +0000 (GMT) Message-ID: <7540526.1149790191621.JavaMail.jira@brutus> Date: Thu, 8 Jun 2006 18:09:51 +0000 (GMT+00:00) From: "Christopher G. Stach II (JIRA)" To: activemq-dev@geronimo.apache.org Subject: [jira] Commented: (AMQ-738) Broker does not recognize failed broker upon reconnect In-Reply-To: <27593887.1149693111482.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ https://issues.apache.org/activemq/browse/AMQ-738?page=comments#action_36267 ] Christopher G. Stach II commented on AMQ-738: --------------------------------------------- Here's the broker config: classpath:/application.properties SYSTEM_PROPERTIES_MODE_OVERRIDE multicast://${amq.serviceName} ${java.io.tmpdir}/${amq.dataDir} 2 vm://${amq.brokerName} multicast://${amq.serviceName} tcp://${amq.bindAddress}:${amq.bindPort} > Broker does not recognize failed broker upon reconnect > ------------------------------------------------------ > > Key: AMQ-738 > URL: https://issues.apache.org/activemq/browse/AMQ-738 > Project: ActiveMQ > Type: Bug > Components: Broker > Versions: 4.0 > Reporter: Christopher G. Stach II > > > After normal shutdown of a broker and bring it back up, the first broker reports this error: > [11:07:15.162] Establishing network connection between from vm://app1-test?network=true to tcp://10.xxx:49995 > [11:07:15.165] Starting a network connection between vm://app1-test#20 and tcp://null:0 has been established. > [11:07:15.294] Async error occurred: javax.jms.InvalidClientIDException: Broker: app1-test - Client: NC_app2-test_inboundapp1-test already connected > [11:07:15.294] javax.jms.InvalidClientIDException: Broker: app1-test - Client: NC_app2-test_inboundapp1-test already connected > [11:07:15.294] at org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176) > [11:07:15.294] at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69) > [11:07:15.294] at org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69) > [11:07:15.294] at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69) > [11:07:15.294] at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82) > [11:07:15.294] at org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507) > [11:07:15.294] at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118) > [11:07:15.294] at org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201) > [11:07:15.294] at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62) > [11:07:15.294] at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97) > [11:07:15.294] at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63) > [11:07:15.294] at org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76) > [11:07:15.294] at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44) > [11:07:15.294] at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60) > [11:07:15.294] at org.apache.activemq.network.DemandForwardingBridgeSupport.startLocalBridge(DemandForwardingBridgeSupport.java:192) > [11:07:15.294] at org.apache.activemq.network.DemandForwardingBridgeSupport$3.run(DemandForwardingBridgeSupport.java:162) > [11:07:15.327] Network connection between vm://app1-test#20 and tcp://app2.xxx/10.xxx:49995(app2-test) has been established. > [11:07:15.347] Unexpected local command: ConnectionError {commandId = 2, responseRequired = false, connectionId = null, exception = javax.jms.InvalidClientIDException: Broker: app1-test - Client: NC_app2-test_inboundapp1-test already connected} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira