Hi You would need to use a transaction manager that supports both JMS and JDCB - eg being XA capable. (2 phase commit).
Then configure your routes to use the same TX manager. On Fri, Feb 22, 2013 at 10:59 AM, Neeraj Mahajan <neeraj.maha...@specsavers.com> wrote: > 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 which is using Hibernate transaction manager. > > The issue I am facing is my transaction policy for Hibernate transaction > manager is not working when I am using transaction policy for JMS > transaction manager in the first route. > > If i remove the JMS transaction policy in the first route, my Hibernate > transaction policy works in the second route. > > This problem I am facing in camel 2.6 , but in camel 1.6 everything is > working perfectly. > > Please suggest. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Issue-with-using-multiple-transaction-managers-of-different-types-on-two-different-routes-in-same-cal-tp5728012.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
