I have an application that performs the Routes management Camel. Basically we add / remove routes on the basis of a specific logic.
One of these routes possesses one idempotentConsumer. If I add and remove this route JdbcMessageIdRepository the service remains in context. So if I repeat the addition operation and removal of the route (often) I have a memory leak. <http://camel.465427.n5.nabble.com/file/n5777242/JdbcMessageIdRepository.png> -- View this message in context: http://camel.465427.n5.nabble.com/Leak-of-Memory-using-JdbcMessageIdRepository-tp5777242.html Sent from the Camel - Users mailing list archive at Nabble.com.