Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 63670 invoked from network); 29 Oct 2007 21:53:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Oct 2007 21:53:45 -0000 Received: (qmail 72143 invoked by uid 500); 29 Oct 2007 21:53:32 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 72124 invoked by uid 500); 29 Oct 2007 21:53:32 -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 72115 invoked by uid 99); 29 Oct 2007 21:53:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2007 14:53:32 -0700 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; Mon, 29 Oct 2007 21:53:35 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1ImcXq-00045c-Ky for users@activemq.apache.org; Mon, 29 Oct 2007 14:53:14 -0700 Message-ID: <13477767.post@talk.nabble.com> Date: Mon, 29 Oct 2007 14:53:14 -0700 (PDT) From: tpounds To: users@activemq.apache.org Subject: InvalidClientIDException when using valid NetworkConnectors in activemq.xml MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: trevor.pounds@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org I'm seeing a weird problem when using static network connectors in the latest 5.0 snapshots. If i specify the following in my activemq.xml. The following happens when my local broker is running activemq 5.0 and the upstream servers are using 4.1.1 or 5.0-SNAPSHOT. I also see the issue when using 4.1.1 instances but the error message is less verbose than the one listed below. or I will see a pretty verbose stack trace with the following errors (5.0-SNAPSHOT): WARN TransportConnection - Failed to add Connection javax.jms.InvalidClientIDException: Broker: localhost- Client: NC_localhost_inboundlocalhost already connected from vm://localhost#0 a little bit further down I see the following Async error occurred: javax.jms.InvalidClientIDException: Broker: localhost- Client: NC_localhost_inboundlocalhost already connected from vm://localhost#0 It continues to show this for a few times and then stops. I haven't tested to see if the connections between the upstream brokers is connected, so I'm not sure if this is affecting any use cases. I will try to post back with more information regarding this. The 4.1.1 instance shows the following...it seems to be the same sort of error. INFO DemandForwardingBridge - Network connection between vm://localhost#2 and tcp://server2:61616 shutdown due to local error: javax.jms.InvalidClientIDException: Broker: localhost- Client: NC_localhost_inboundlocalhost already connected -- View this message in context: http://www.nabble.com/InvalidClientIDException-when-using-valid-NetworkConnectors-in-activemq.xml-tf4714929s2354.html#a13477767 Sent from the ActiveMQ - User mailing list archive at Nabble.com.