Skip to content

Include root cause when MySQLMaxValueIncrementer fails to commit #37389

Closed

Description

@sbrannen

Overview

When useNewConnection is true, MySQLMaxValueIncrementer commits the sequence update on a separate connection. If that commit (or the subsequent restoration of auto-commit) fails, a DataAccessResourceFailureException is thrown, but the original SQLException is discarded.

This makes it unnecessarily difficult to diagnose the actual cause of the failure.

We should therefore include the original SQLException as the cause of the DataAccessResourceFailureException.

Related Issues

Activity

  1. self-assigned this
    on Oct 4, 2026
  2. added this to the 7.1.0-RC1 milestone on Oct 4, 2026
  3. added a commit that references this issue on Oct 4, 2026
    cc8f1d3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

in: dataIssues in data modules (jdbc, orm, oxm, tx)type: enhancementA general enhancement

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions