Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 4399 invoked from network); 22 Jun 2006 09:18:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Jun 2006 09:18:54 -0000 Received: (qmail 81905 invoked by uid 500); 22 Jun 2006 09:18:54 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 81742 invoked by uid 500); 22 Jun 2006 09:18:53 -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 81733 invoked by uid 99); 22 Jun 2006 09:18:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 02:18:53 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of james.strachan@gmail.com designates 72.14.214.205 as permitted sender) Received: from [72.14.214.205] (HELO hu-out-0102.google.com) (72.14.214.205) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 02:18:51 -0700 Received: by hu-out-0102.google.com with SMTP id 28so145751hug for ; Thu, 22 Jun 2006 02:18:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hktXneQo8vsKNrfSKsrIa2r0kaA6u41rfzcaIJMDl4OdxAGo47HiQXjSIwdoYZQNvIvSck1t0JCoT3Qsq7Lt6Zpj4oKwJyN7jIoHk4QyV8DMViGQjYQH+XRq9zmbUuxqQvaydund/a1zA7+PJ5paWJd7+LyLbjXTu4uQl5U8OpY= Received: by 10.66.244.10 with SMTP id r10mr828981ugh; Thu, 22 Jun 2006 02:18:30 -0700 (PDT) Received: by 10.66.224.1 with HTTP; Thu, 22 Jun 2006 02:18:30 -0700 (PDT) Message-ID: Date: Thu, 22 Jun 2006 11:18:30 +0200 From: "James Strachan" To: activemq-users@geronimo.apache.org Subject: Re: list transport with vm In-Reply-To: <4973427.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4973427.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N sounds like a bug - I wonder do you get the same issue in 4.0? On 6/21/06, jerb wrote: > > I'm using 3.2 and I get different behavior when creating a connection using > transport url - "list:(vm://brokername)" than when using "vm://brokername". > The difference appears to be that the former always creates a new embedded > broker while the latter will reuse an existing broker. The result is that > clients intending to use "vm://brokername" as the transport won't be able to > transmit messages to eachother if one of them was configured in a list. > Looking at the code, the reason appears to be that the > ActiveMQConnectionFactory looks into the brokerContext to check for an > existing broker connector, while the CompositeTransportChannel does not. > Why the difference in behavior? > -- > View this message in context: http://www.nabble.com/list-transport-with-vm-t1823631.html#a4973427 > Sent from the ActiveMQ - User forum at Nabble.com. > > -- James ------- http://radio.weblogs.com/0112098/