Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 81277 invoked from network); 7 Jul 2006 19:51:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Jul 2006 19:51:08 -0000 Received: (qmail 22457 invoked by uid 500); 7 Jul 2006 19:51:07 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 22428 invoked by uid 500); 7 Jul 2006 19:51:07 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 22419 invoked by uid 99); 7 Jul 2006 19:51:07 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jul 2006 12:51:07 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jul 2006 12:50:55 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1FywL0-0005Ei-EB for activemq-users@geronimo.apache.org; Fri, 07 Jul 2006 12:50:06 -0700 Message-ID: <5223575.post@talk.nabble.com> Date: Fri, 7 Jul 2006 12:50:06 -0700 (PDT) From: srodrigues To: activemq-users@geronimo.apache.org Subject: Re: Client: XXX already connected bug In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-Sender: srodrigues@wilshire.com X-Nabble-From: srodrigues References: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Not sure if this is still an issue, I was facing the same "already connected" problem even with 4.0 and 4.0.1 and I just switched from DefaultMessageListenerContainer to SimpleMessageListenerContainer and it worked fine with no such exception. I could get this to work by replacing the DefaultMessageListenerFactory with the SimpleMessageListenerFactory class and there were no more hung servers. Side Note: I have had six listener containers and each one listens to a different Queue. This configuration works if I assign concurrentConsumers in each of these listener containers equal to 1. ( 6 x 1 = 6. ) If I assign concurrentConsumers in each of these listener containers to 2. (6 x 2 = 12 ) When I do this two listener consumers do not receive the message, implying there is a some limit on the total number of concurrentConsumers in such a configuration. -- View this message in context: http://www.nabble.com/Client%3A-XXX-already-connected-bug-tf1522491.html#a5223575 Sent from the ActiveMQ - User forum at Nabble.com.