Bug #91351 | MysqlConnectionPoolDataSource - autocommit status lost if global autocommit = 0 | ||
---|---|---|---|
Submitted: | 21 Jun 2018 11:23 | Modified: | 13 Sep 2023 21:38 |
Reporter: | Ceyhan Kasap | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | mysql-connector-java-8.0.11 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[21 Jun 2018 11:23]
Ceyhan Kasap
[22 Jun 2018 8:24]
Chiranjeevi Battula
Hello Ceyhan Kasap, Thank you for the bug report and testcase. Verified this behavior on MySQL Connector / J 8.0.11. Thanks, Chiranjeevi.
[13 Sep 2023 21:38]
Daniel So
Posted by developer: Added the following entry to the Connector/J 8.2.0 changelog: "Obtaining a connection from a MysqlConnectionPoolDataSource made Connector/J reset its connection state unless the connection property paranoid was set to be true. During the reset, the autocommit mode of the session was restored to the default value specified on the server by the system variable autocommit, while the JDBC specification mandates that autocommit be always enabled for a freshly created connection. With this patch, the connection reset will always enable autocommit in the situation."