You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@grails.apache.org by GitBox <gi...@apache.org> on 2026/06/18 00:10:11 UTC

[GH] (grails-core/feat/mongo-server-transactions): Workflow run "CI - Groovy Joint Validation Build" failed!

The GitHub Actions job "CI - Groovy Joint Validation Build" on grails-core.git/feat/mongo-server-transactions has failed.
Run started by GitHub user codeconsole (triggered by codeconsole).

Head commit for run:
dfe1234cf68023f6ac4765042b5e57a96e1131a5 / Scott Murphy Heiberg <sc...@alwaysvip.com>
Add opt-in MongoDB multi-document transactions to GORM for MongoDB

GORM for MongoDB previously treated a transaction as a client-side flush
boundary: pending writes were batched and flushed on commit, but each write
auto-committed individually and nothing rolled back when a later operation failed.

This adds real server-side transactions backed by a com.mongodb.client.ClientSession.
When grails.mongodb.transactional is enabled (default false), a GORM transaction
starts a ClientSession and MongoDB transaction and every read and write for the
session runs within it, committing or aborting atomically. A new MongoTransaction
drives the commit (retrying on an UnknownTransactionCommitResult) and the abort, and
closes the session afterwards.

The feature is opt-in and degrades gracefully: a standalone topology is detected at
runtime and falls back to the legacy flush-only behavior with a one-time warning.
Identifier generation for native Long ids is intentionally left non-transactional,
mirroring the semantics of database sequences.

Report URL: https://github.com/apache/grails-core/actions/runs/27725146077

With regards,
GitHub Actions via GitBox