Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 10688 invoked from network); 12 Nov 2007 05:37:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Nov 2007 05:37:21 -0000 Received: (qmail 13159 invoked by uid 500); 12 Nov 2007 05:37:08 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 13129 invoked by uid 500); 12 Nov 2007 05:37:08 -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 13120 invoked by uid 99); 12 Nov 2007 05:37:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Nov 2007 21:37:08 -0800 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, 12 Nov 2007 05:37:10 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1IrRyb-0005Oh-Ni for users@activemq.apache.org; Sun, 11 Nov 2007 21:36:49 -0800 Message-ID: <13699873.post@talk.nabble.com> Date: Sun, 11 Nov 2007 21:36:49 -0800 (PST) From: rajesha_s To: users@activemq.apache.org Subject: Re: Using static Transport - messages not reliably reaching consumers on different machines In-Reply-To: <13296795.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: rajeshs@coreobjects.com References: <13296795.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Looks like the problem seems to be with the use of wild cards. This certainly is a defect and probably needs to be fixed. It took quite sometime to really identify this issue. For now I am working around by not using wildcards in the topic names. I am hoping that this is fixed in the next release. rajesha_s wrote: > > I have two brokers configured to use the static transport on two different > machines. > I have producers sending messages on each of the machines sending messages > to specific topics to the local broker. > Also, I have consumers that are configured to recieve messages on each of > these boxes as follows - > > Machines - A and B > Producer on A publishes to two topics as follows > message1.A and message2.A > Producer on B publishes to two topics as follows > message1.B and message2.B > > Consumer on A listens for following topics > message1.A and message2.* (we want to subscribe to message2 from both the > machines A and B) > > Consumer on B listens for the following topics > message1.B and message2.* (we want to subscribe to message2 from both the > machines A and B) > > The problem I am facing is the message2 does not get delivered > consistently from the other box. Sometimes it works but sometimes it just > does not come through > > Environment - > Active MQ version 4.1.1 > JDK 1.5/1.6 > > the broker configuration is as below > > > > > > > > > > > uri="static://(tcp://host1:62002,tcp://host2:62002)"/> > > > > > > > The clients connect using the url tcp://localhost:62002. > > Looking forward for a solution here. > Thanks in advance. > -- View this message in context: http://www.nabble.com/Using-static-Transport---messages-not-reliably-reaching-consumers-on-different-machines-tf4653981s2354.html#a13699873 Sent from the ActiveMQ - User mailing list archive at Nabble.com.