Thanks, I've upgraded to Camel 2.9.2 and that seems to have resolved the memory leak. It seems that there were FileConsumer objects being held onto in the threadpool with a few being created (and not released) every few minutes.
-- View this message in context: http://camel.465427.n5.nabble.com/Memory-leak-with-Camel-JMX-DefaultMBeanServerInterceptor-tp5714271p5715088.html Sent from the Camel - Users mailing list archive at Nabble.com.
