davsclaus commented on PR #27681: URL: https://github.com/apache/camel/pull/27681#issuecomment-6125485589
Thanks @oscerd, addressed in 53b4dd164fee (rebased on main, which now has the 4.24 guide): - `isRollbackOnlyLast()`: yes, intended, for the reason you give: `TransactionErrorHandler` consumes the flag, so when it reaches the consumer, the consumer's own transaction is the last one. The follow-up to align camel-sql, camel-mybatis and camel-jooq is CAMEL-25588. - The jpa doc and the upgrade note now say the entity is consumed again only while it still matches the query, and that with `transacted=false` what a `@PreConsumed` method changed is committed with the poll (with `transacted=true` it is rolled back with the poll). - The upgrade note now says that a message the route always marks rollback only, which was removed before, is consumed again at every poll (JPA) or taken again at once (transacted Hazelcast SEDA). Applying `onErrorDelay` after a rollback in `done()` is CAMEL-25589. - Log wording: kept as is. - `HazelcastSedaTransactedRollbackOnlyTest` did run in CI: the incremental-test log of run 38224556027 shows it (1 test) and `JpaConsumerRollbackOnlyTest` (3 tests), all passing. _Claude Code on behalf of @davsclaus._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
