Seems like I was too quick to pull the trigger on that one. I wasn't defining any log4j configuration in my test case and this cause the debug to be turned on, but not outputted. The SLF4J debug method takes an Object and not a String for its argument, so toString() will not be called when evaluating the argument list. Supplying a log4j.properties fixed this performance issue. So no modification required in the Camel code base.
My apologies for this. Thanks -- View this message in context: http://camel.465427.n5.nabble.com/Little-ProducerCache-performance-improvement-when-dealing-with-long-URIs-tp5731282p5731288.html Sent from the Camel Development mailing list archive at Nabble.com.
