Re: Another problem?

2011-05-05 Thread Muhammad Ichsan
On Wed, May 4, 2011 at 8:47 PM, Muhammad Ichsan ich...@gmail.com wrote: On Wed, May 4, 2011 at 7:26 PM, Claus Ibsen claus.ib...@gmail.com wrote: Read the documentation from(xxx) .inOut().to(activemq:queue:foo) .threads(5) .to(yyy) .to(zzz);

Re: Another problem?

2011-05-05 Thread Claus Ibsen
You need to put stuff inside the threads tag. threads XXX /threads I think in one of the later Camel releases we have added validation for that so you will get an error on startup. On Thu, May 5, 2011 at 8:14 AM, Muhammad Ichsan ich...@gmail.com wrote: On Wed, May 4, 2011 at 8:47 PM,

Re: Another problem?

2011-05-05 Thread Muhammad Ichsan
On Thu, May 5, 2011 at 1:14 PM, Muhammad Ichsan ich...@gmail.com wrote: Using above DSL, it did work. But it does not for the following XML:                route                        from uri=direct:casemx /                        setExchangePattern pattern=InOut /                        

Another problem?

2011-05-04 Thread Muhammad Ichsan
Dear All I found another problem in Camel. Given context file (the java bean code is self-explainable): route from uri=direct:casemx / setExchangePattern pattern=InOut / to uri=activemq:preparation

Re: Another problem?

2011-05-04 Thread Claus Ibsen
to the direct:casemx endpoint and have concurrent threads process messages in that route. On Wed, May 4, 2011 at 1:02 PM, Muhammad Ichsan ich...@gmail.com wrote: Dear All I found another problem in Camel. Given context file (the java bean code is self-explainable): route from

Re: Another problem?

2011-05-04 Thread Claus Straube
On 04.05.2011 13:02, Muhammad Ichsan wrote: Dear All I found another problem in Camel. Given context file (the java bean code is self-explainable): route from uri=direct:casemx / setExchangePattern pattern=InOut / to uri

Re: Another problem?

2011-05-04 Thread Muhammad Ichsan
2011/5/4 Claus Ibsen claus.ib...@gmail.com: Hi Its a bit hard to follow your question? Concurrency all starts with consumers. So if you have a single thread that sends a message to direct:casemx then there is only a single thread processing in that given route. This is how I send the

Re: Another problem?

2011-05-04 Thread Muhammad Ichsan
On Wed, May 4, 2011 at 6:27 PM, Muhammad Ichsan ich...@gmail.com wrote: 2011/5/4 Claus Ibsen claus.ib...@gmail.com: Hi It's still in sequence manner, even for this code: ExecutorService executor = Executors.newFixedThreadPool(10); // When: 18 messages are sent

Re: Another problem?

2011-05-04 Thread Claus Ibsen
Read the documentation See request/reply over JMS http://camel.apache.org/jms On Wed, May 4, 2011 at 2:21 PM, Muhammad Ichsan ich...@gmail.com wrote: On Wed, May 4, 2011 at 6:27 PM, Muhammad Ichsan ich...@gmail.com wrote: 2011/5/4 Claus Ibsen claus.ib...@gmail.com: Hi It's still in

Re: Another problem?

2011-05-04 Thread Muhammad Ichsan
On Wed, May 4, 2011 at 7:26 PM, Claus Ibsen claus.ib...@gmail.com wrote: Read the documentation See request/reply over JMS http://camel.apache.org/jms Thank you so much Claus! This is what I've been looking for. from(xxx) .inOut().to(activemq:queue:foo) .threads(5) .to(yyy) .to(zzz); I'll