Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 50EAF1035F for ; Sat, 15 Feb 2014 00:59:52 +0000 (UTC) Received: (qmail 10313 invoked by uid 500); 15 Feb 2014 00:59:51 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 10281 invoked by uid 500); 15 Feb 2014 00:59:51 -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 10271 invoked by uid 99); 15 Feb 2014 00:59:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Feb 2014 00:59:50 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Feb 2014 00:59:45 +0000 Received: from joe.nabble.com ([192.168.236.139]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WETbI-0003te-FB for users@activemq.apache.org; Fri, 14 Feb 2014 16:59:24 -0800 Date: Fri, 14 Feb 2014 16:59:24 -0800 (PST) From: artnaseef To: users@activemq.apache.org Message-ID: <1392425964437-4678008.post@n4.nabble.com> In-Reply-To: References: Subject: Re: already connected from tcp://xx.xxx.x.xxx:59357 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Is the client code setting a Client ID on the connection via setClientID()? http://docs.oracle.com/javaee/1.4/api/javax/jms/Connection.html#setClientID(java.lang.String) If so, then only one connection with a specific client ID can connect to the broker/network-of-brokers at any one time. Given the error message indicating already connected, you can see from where the other connection is being made. If that's the same machine and the same JVM, check for a connection pool, or connection leak on the client. -- View this message in context: http://activemq.2283324.n4.nabble.com/already-connected-from-tcp-xx-xxx-x-xxx-59357-tp4678001p4678008.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.