camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "PLANAMENTE Michael EXT-OD" <>
Subject Problem with multiple coma separated endpoints defined in the same URI
Date Thu, 03 Jan 2013 15:14:45 GMT
Hi all,

I've experienced a strange behavior when I declared multiple endpoints in the same URI. (All
endpoints are coma separated.)
See below for explanations...

Using this java code:
I'd like to send messages to all endpoints defined in outEndpoint (like a pipeline)

With, in config file:
inEndpointURI =activamq:queue:xyz (the problem is not here)
outEndpointURI = activemq:queue:blah,file://path  (the problem is here!)

with, in spring file:
camel context declaring the outEndpoint's URI attribute pointing to outEndpointURI.(nothing
special here)

In java file:
Endpoint outEndpoint;


The strange behaviour:
The endpoint detects there are 2(in this case) different endpoints BUT consider all declared
subsequent endpoints as being of the first(in this case activemq) endpoint's type! In other
words, the file is considered as an activemq queue and I have a queue named  "file://path<file:///\\path>"
in the amq broker!

Camel version: Camel 2.8.0

Any idea?

Many thanks,
Michael Planamente


Atos Worldline SA/NV - Chaussee de Haecht 1442 Haachtsesteenweg
- 1130 Brussels - Belgium
RPM-RPR Bruxelles-Brussel - TVA-BTW BE 0418.547.872
Bankrekening-Compte Bancaire-Bank Account 310-0269424-44
BIC BBRUBEBB - IBAN BE55 3100 2694 2444

"The information contained in this e-mail and any attachment thereto is confidential and may
contain information which is protected by intellectual property rights.
This information is intended for the exclusive use of the recipient(s) named above.
This e-mail does not constitute any binding relationship or offer toward any of the addressees.
If you are not one of the addressees , one of their employees or a proxy holder entitled to
hand over this message to the addressee(s), any use of the information contained herein (e.g.
reproduction, divulgation, communication or distribution,...) is prohibited.
If you have received this message in error, please notify the sender and destroy it immediately
The integrity and security of this message cannot be guaranteed and it may be subject to data
corruption, interception and unauthorized amendment, for which we accept no liability."

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message