Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 28559 invoked from network); 1 Sep 2010 10:24:08 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Sep 2010 10:24:08 -0000 Received: (qmail 19399 invoked by uid 500); 1 Sep 2010 10:24:08 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 19192 invoked by uid 500); 1 Sep 2010 10:24:06 -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 19184 invoked by uid 99); 1 Sep 2010 10:24:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Sep 2010 10:24:05 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Sep 2010 10:24:02 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o81ANfs0009150 for ; Wed, 1 Sep 2010 10:23:41 GMT Message-ID: <29219244.6091283336621036.JavaMail.jira@thor> Date: Wed, 1 Sep 2010 06:23:41 -0400 (EDT) From: "Gary Tully (JIRA)" To: dev@activemq.apache.org Subject: [jira] Assigned: (AMQ-2831) Set ClientID - InvalidClientIDException with http transport In-Reply-To: <16764733.43581279280991887.JavaMail.jira@thor> 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-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-2831: ------------------------------- Assignee: Gary Tully > Set ClientID - InvalidClientIDException with http transport > ----------------------------------------------------------- > > Key: AMQ-2831 > URL: https://issues.apache.org/activemq/browse/AMQ-2831 > Project: ActiveMQ > Issue Type: Bug > Components: Transport > Affects Versions: 5.3.2 > Reporter: Colombo Marco > Assignee: Gary Tully > Priority: Blocker > Fix For: 5.4.1 > > Attachments: broker-config.xml, TestVaseClientID.zip > > > I have a client that do a durable subscriptio to a topic. > It register with a static client id. > After a connectivity loss (an so a new re-connection), this exception is thrown and connection cannot be > re-established: > 2010-07-15 13:49:04,700 ERROR - javax.jms.InvalidClientIDException: Broker: localhost - Client: (SchedulerId = '1') already connected from blockingQueue_8461294 > at org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:216) > at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82) > at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82) > at org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:77) > at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82) > at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:82) > .... > This is not possible, because is the only client with that name and previos connection was closed . .close(). > If I kill all the clients an I leave active only the broker, > If I try to reconnect using http (or tcp) I get the same error. > So client is not de-registered. > This appens also if I use failover protocol. After client kill/restart. Same exception is raised (javax.jms.InvalidClientIDException - with the clientID of the killed client). > I have to restart broker in order to register again the client. > A test case is attached. > If you connect to http the first time, connection is ok. > If you kill the JVM and the try to restart the test case, 'myclid already connected from blockingQueue_' is always raised. Also after some hours. I have to restart the broker in order to have a new conection with that client id. > This test simulate a JVM crash with no resource cleanup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.