Im using the jpa component as a consumer to poll a table. The batchsize of each poll is set to eg. 100 as :
<from uri="jpa:org.apache.camel.MyEntity?consumer.query=select x from org.apache.MyEntity x order by sekvens&maximumResults=100&consumeLockEntity=false" /> <transacted/> The route is transacted so at the end the whole batch is either successful, or gets rolled back i there is a problem with any of the records read. It works nicely - the problem is that the jmx statistics on the route logs each exchange as completed even though at the end everything might get rolled back. In my opinion they should be regarded as failed instead. ? Camel version 2.8.1 /preben -- View this message in context: http://camel.465427.n5.nabble.com/Misleading-jmx-statistics-on-jpa-component-tp4960503p4960503.html Sent from the Camel - Users mailing list archive at Nabble.com.
