Re: Using NMR endpoint in an Transacted route

Charles, Claus Thank you very much for your replies It was a great help and it worked perfectly for me, I have also seen "nmr" documentation and I can see It will use the same thread if we enable the synchronous mode while using the nmr endpoint. I am going to use "nmr" with synchronus mode in m

Re: Using NMR endpoint in an Transacted route

Thank you very much Claus, the application transaction issue is now resolved with the direct-vm component. The good thing is that I am using the 2.10 version of camel from which this component has been introduced. -- View this message in context: http://camel.465427.n5.nabble.com/Using-NMR-end

Using NMR endpoint in an Transacted route

I am using JBoss Fuse 6 for deploying my integration application which is composed of multiple bundles. For communication among the routes which are in the separate bundles I am using "nmr" component. When I am calling the NMR endpoint from one of my transacted route ,the called route through NMR

Message headers getting lost while using NMR

My Integration application is divided into two camel contexts. I am using NMR to have integration between these two camel contexts. The flow is as follows and I am using *INOnly* Message Exchange Pattern 1 CamelContext1-Route -> NMR -> CamelContext2-Route 2 CamelContext2-Route set some *new header

Issue with using multiple transaction managers of different types on two different routes in same camel-context.xml

I have one camel route which is listening on an Activmq consumer endpoint and calls another direct route which do some persistence work. In the first route i have injected transaction policy which is using JMS transaction manager and in the second route I have intected other transaction policy whi

Re: Aggregator not propagating exception back in camel version 1.6.2

Thanks Claus Now I think i have to use some thing else intead of aggregator as i cant upgrate the version. Thanks for your valuable support and time. Neeraj Mahajan -- View this message in context: http://camel.465427.n5.nabble.com/Aggregator-not-propagating-exception-back-in-camel-version-1

Re: Aggregator not propagating exception back in camel version 1.6.2

Neeraj Mahajan -- View this message in context: http://camel.465427.n5.nabble.com/Aggregator-not-propagating-exception-back-in-camel-version-1-6-2-tp5717629p5717689.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Aggregator not propagating exception back in camel version 1.6.2

Once aggregated result(exchange) is commited, the control does not come back to the aggregation strategy. And also I dont want to handle the exception, I need it to be progagated back from the aggregator component. Thanks Neeraj Mahajan -- View this message in context: http://camel.465427.n5

Re: Aggregator not propagating exception back in camel version 1.6.2

Thanks again So is there any way in camel 1.6.2, by which we can tell the aggregator not to handle the exception. Neeraj Mahajan -- View this message in context: http://camel.465427.n5.nabble.com/Aggregator-not-propagating-exception-back-in-camel-version-1-6-2-tp5717629p5717683.html Sent

Re: Aggregator not propagating exception back in camel version 1.6.2

issue. Thanks Neeraj Mahajan -- View this message in context: http://camel.465427.n5.nabble.com/Aggregator-not-propagating-exception-back-in-camel-version-1-6-2-tp5717629p5717676.html Sent from the Camel - Users mailing list archive at Nabble.com.

Aggregator not propagating exception back in camel version 1.6.2

I am calling a route from Aggregator using direct component once aggregation is complete. When the called direct route throws any Exception I expect that aggregator *should not handle* that exception, but the problem I am facing is that the exception is being getting handled by the aggregator wh