Hello there! I've been ill hand haven't seen your replies until now.
Yes, we're usin Oracle AQ. I have now discovered that since the DB that the queues resides in is not the same as the one the application operates on we do in fact NOT use transacted JMS. If I remember correctly it was because XA-transactions can be a pain setting up. As a workaround I figured i could just explicitly enqueue the poisoned message on the error-queue provided by AQ. But that is not permitted by AQ. Is there a simple way to make camel use two transactionmanagers? Or perhaps the simplest solution is to just define some new queues and treat them as error-queues? We're planning on migrating to IBM-MQ in the not too distant future so that may be a workable solution. Kind regards Sverre Nyheim -- View this message in context: http://camel.465427.n5.nabble.com/Can-t-get-things-on-Oracle-DB-backout-queue-tp5784298p5784592.html Sent from the Camel - Users mailing list archive at Nabble.com.
