I don't have a small project that reproduces the issue, just the large app I'm performance-tuning now. I'm willing to try anything you recommend to figure out exactly what's wrong. I have a feeling that if I created a smaller project to mock this problem, I wouldn't be able to reproduce it. :)
The interesting thing to note is that all the routes work as expected, the transactional error handler works to retry errors according to the policies we have set. The only indication that something isn't right with these transacted routes is that no statistics get recorded for the processors of those routes in JMX. Charles Moulliard-2 wrote > Do you have a use case that we could use to reproduce the issue ? -- View this message in context: http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tp5757634p5758000.html Sent from the Camel - Users mailing list archive at Nabble.com.
