I do have batch jobs that perform chunk processing. This loop usually continues until the Reader has no more items to read and thus returns null. Or if at any point an Exception is thrown. In this case the batch job fails and the current transaction will be rolled back.

I have some JSR352 jobs running in Wildfly (which uses JBeret). Some time ago I noticed strange behaviour, and now I drilled it down to something that’s puzzling me.