other remark(to simplify your config and to be more "JTA implementation" independent), I see you're using Atomikos pools... this is ABSOLUTELY not manatory, you can use dbcp. using DBCP, you'll have to provide dbcp the transactionManager parameter + driverClassName with an XA version of driver(oracle.jdbc.xa.client.OracleXaDataSource) for example.
dbcp, when aware of a transactionManager, is able to enlist the requested connections into current transaction... doing so will also avoid Atomikos pools to keep an in memory map of all declared pools(through unique name parameter) that can provoke unexpected results (depending on how you configured it -> you might have to clean that map each time you restart your bundle as Atomikos keeps track of the instance you created during the previous run. ) Michael. -- View this message in context: http://camel.465427.n5.nabble.com/Need-help-with-Camel-JPA-Atomikos-tp5713578p5713657.html Sent from the Camel - Users mailing list archive at Nabble.com.
