Nice... While the bug is not resolved to the idempotent of the problem I will use the workaround that I said. But in relation to the producer, is there any workaround possible?
Thank you. -- View this message in context: http://camel.465427.n5.nabble.com/Leak-of-Memory-using-JdbcMessageIdRepository-tp5777242p5777293.html Sent from the Camel - Users mailing list archive at Nabble.com.
