Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Sat, 4 Jan 2014 19:28:14 -0800 (PST)
From: artnaseef <art@artnaseef.com>
To: users@activemq.apache.org
Message-ID: <1388892493990-4676016.post@n4.nabble.com>
In-Reply-To: 
 <CAKS7T5MTkR0=1rtrGp4Me=C0FQyWxyGATXq-Kqrk22RYwKSjaQ@mail.gmail.com>
References: <1388392872440-4675895.post@n4.nabble.com>
 <CAKS7T5MTkR0=1rtrGp4Me=C0FQyWxyGATXq-Kqrk22RYwKSjaQ@mail.gmail.com>
Subject: Re: EndPoint URI issue
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Assuming there are two different brokers in your setup - one for DEV and one
for INT...

It sounds like both producer endpoints are sending to the same broker (DEV)
- can you confirm that?

If so, the connection factory setup for the "activemq" component defines the
broker to which the endpoint is connecting.  To have one camel context use
two different brokers, you'll need two different component configurations,
such as "activemq1" and "activemq2".

Regardless of the number of brokers - try checking the camel configuration
at runtime using an MBean browser.  You should be able to confirm the
endpoints for the routes, and also confirm that messages are passing through
the correct routes.


--
View this message in context: http://activemq.2283324.n4.nabble.com/EndPoint-URI-issue-tp4675895p4676016.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.