Hi Christian, Thank you very much for providing a comprehensive example of tracing. As it turns out there was an error message produced at the top of the output from my tests which I had not understood the significance of...
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. When your known-good example produced this error as well I figured it must somehow be related to the lack of tracing output. The problem is that tracing depends on the presence of SLF4j, which I did not have in my project. I added this to my pom.xml and now tracing works: <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.7.2</version> </dependency> Please consider adding a note about this to the tracer documentation. (Or if it's there already, maybe it could be highlighted, because I didn't see it.) Thanks again for all the help. I will go back to pursuing the bug in my application, now with the benefit of the tracer logs. Best regards, -louis -- View this message in context: http://camel.465427.n5.nabble.com/global-onException-only-works-for-first-to-route-item-but-nothing-after-that-tp5724296p5724402.html Sent from the Camel - Users mailing list archive at Nabble.com.
