Hi,
i try to process in parallel 2 http request using SEDA component, but
only one message at time is processed.
Here my configuration, where i set concurrentConsumers=2 :
from(direct:parallelDirect)
.split(body(ArrayList.class))
.to(seda:parallelSeda?concurrentConsumers=2)
@Henryk: Yes, that works fine for message headers, I use it a lot to pass
expected message headers. But it is not possible for Exchange properties.
Are you sure? :) Exchange properties are propagated as well as
headers. Can you show me an example, where the properties are not
propagated down
Hi,
You don’t need to let the Slave run when the Master is in charge.
I think you can take a look at the camel-zookeeper[1].
The other two options for singleton clustering are:
a) Master component [1] from Fuse Fabric [2] (if you deploy your
application on Karaf/ServiceMix)
b) JGroups
So You mean to say Without creating Client, Its not possible to called Web
Service?
--
View this message in context:
http://camel.465427.n5.nabble.com/SOAP-Web-service-Calling-using-camel-tp5745180p5745379.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi guys,
Does this mean I need to manage sending messages to the DLQ from within the
route in the error handler?
No, the DLQ handler definition (deadLetterChannel(jms:queue:dead))
is all you need. No extra wiring is required. Other routes don't need
to be aware of the DQL definition.
As far
Dear,
Thanks for your help.
I have Tested my Web Service using
*exchange.getIn().setBody(soap:Envelope
xmlns:soap=\http://schemas.xmlsoap.org/soap/envelope/\;
+ soap:Bodyns1:getApplication
xmlns:ns1=\http://cxf.component.camel.apache.org/\;
+
Seda supports parallel processing but on the consumer side.
So if you have:
from(seda:parallelSeda?concurrentConsumers=2)
.to(...)
this route will process two messages in parallel.
Looking at your route, you don't need seda endpoint to make it parallel,
you can simply replace seda with
ActiveMQ or WebSphere MQ?
On Monday, December 30, 2013, Preethi wrote:
Hi
We are trying to setup Master slave for ActiveMQ using camel-context. Our
current architecture is like this.
1. A camel route which subscribes to MQ topics (these MQ topics are IBM
topics).
2. This camel
Have a basic question about setting up AMQ and Camel context-based routing.
We added a Camel's content based routing for ActiveMQ message systems,
but the system stops throttling when the pending messages bellow a
specific threshold ( approx ~600)
the CBR details
