Thanks and yes, I think you are fully right. It must be camel is building up the memory. In fact that is what it shows up on the camel monitor anyway!. I was confused myself!
I was reading your link and it looks promising alright. I looked up the "Database Sample" and it seems that it could solve my scenario. I am going to setup the Spring TM to mark the route as transacted and we'll see how it goes. Thus theoretically, if I shutdown the database, ActiveMQ should use KahaDB to persist those non committed messages by Camel. Anyway, I'll post the results in a few days. Cheers -- View this message in context: http://activemq.2283324.n4.nabble.com/On-disk-persisted-message-queues-on-consumer-failure-tp4657706p4657730.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
