hutiefang76 opened a new pull request, #549: URL: https://github.com/apache/commons-dbcp/pull/549
Fixes [DBCP-522](https://issues.apache.org/jira/browse/DBCP-522). If a driver changes auto-commit and then a setter or follow-up getter throws an `Error`, the wrapper can keep reporting its previous cached value. Invalidate that value before delegating. The original exception handler and the successful-path read of the actual driver state remain unchanged. Five tests use real H2 memory connections with controlled failures. They cover errors after the state change and from the follow-up getter, plus normal, `SQLException`, and cache-disabled controls. These simulate the failure boundary; they do not reproduce a real driver out-of-memory failure. - Before the fix: 43 focused tests, two regression failures, no errors or skips. - Java 17: the required default `mvn` build passes, including 1610 tests (nine existing disabled cases), license, compatibility, style, static analysis, coverage and Javadoc checks. - Real Java 8: clean compile and all 43 focused tests pass. AI-generated description. Codex and DeepSeek assisted the investigation, implementation, tests and review; the actual diff and executed results were checked before submission. -- 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]
