You might be having issues with ActivMQ flow control. I blogged about similar problem a while back. http://www.dragishak.com/?p=254
Basically, there is a limit on the total number of messages buffered in AMQ. In a transacted route a message will not be taken off the queue unless the transaction is successful. But you can't complete the transaction because, since all the resources are taken, you can't place the message on the next queue. On Mar 14, 2011, at 12:43 PM, Brian wrote: I am having an issue with a message being stuck in an ActiveMQ queue when using spring JTA Transaction Manager backed by Atomikos and a propagation policy of "PROPAGATION_REQUIRES_NEW". I am trying to consume from one queue and insert into the second queue using a different transaction than the first. This issue does not appear on the first message but does on each subsequent message sent. We suspect there is something wrong with the transactions and it is potentially not committing successfully or hanging. Below is my stripped down camel configurations to reproduce this issue. Thanks. Camel Version - 2.6.0 ActiveMQ Version - 5.4.2 Spring Version - 3.0.5 Atomikos Version - 3.7.0 -- View this message in context: http://camel.465427.n5.nabble.com/ActiveMQ-stuck-message-using-JTA-Transactions-tp3595142p3595142.html Sent from the Camel - Users mailing list archive at Nabble.com<http://Nabble.com>.
