Hi, That fears me, as I'm already running with camel 2.8.0 in a production environment since 2 days (JBoss 5.1.0).
I've got my routes in Java-DSL and the relevant spring config is something like http://camel.465427.n5.nabble.com/file/n4622462/xyz.xml xyz.xml Am I affected by this issue? The only reason why I used the the propertyPlaceholder was just because of the configuration ability of the port, just for the case if the port is already in use on the production box. I can't go for a 2.9-SNAPSHOT nightly-build as it seems too risky to me. Should I really disable caching and roll-out a patch release of the application. Any advice? Regards, Babak -- View this message in context: http://camel.465427.n5.nabble.com/LRUCache-memory-leak-when-using-camel-properties-file-tp4621357p4622462.html Sent from the Camel - Users mailing list archive at Nabble.com.
