@Claus +1 This would be really helpfull.
In addition to the problem you laid out I can tell that consuming 100 rows -> processing the 70 building a xml payload -> put in on a jms queue and then on the 71 have an error that rolles everything back ultimately can fill up the redolog off the db and bring it to it's knees. Because of this we only consume one record at the time + have a onException handler with backoff. preben -- View this message in context: http://camel.465427.n5.nabble.com/Misleading-jmx-statistics-on-jpa-component-tp4960503p4994706.html Sent from the Camel - Users mailing list archive at Nabble.com.
