This is a real value-add to many projects! Great news. How much of the re-start challenge facing MDB-triggered multi-commit batches is solved out-of-the-box? Thinking of a batch processing a large inbound message, committing every 10 logical messages, hit by a server crach. After start-up the roll-backed message hits the business logic a second time, which needs to fast-forward to the first logic record of the roll-backed transaction.