Bug #113509 | closeOnCompletion cause no statement reuse and server memory leak | ||
---|---|---|---|
Submitted: | 25 Dec 2023 8:13 | Modified: | 7 Oct 2024 22:17 |
Reporter: | wanyun zhou | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 8.0.33 8.1.0 8.2.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | closeOnCompletion, no statement reuse, server memory leak |
[25 Dec 2023 8:13]
wanyun zhou
[4 Jan 2024 12:02]
Filipe Silva
Hi Wanyun Zhou, Thank you for taking the time to report this issue and for the test case. Verified as described. Statement close is being triggered but neither the statement is effectively closed nor it is being cached.
[7 Oct 2024 22:17]
Daniel So
Posted by developer: Added the following entry to the Connector/J 9.1.0 changelog: "Setting closeOnCompletion() on a PreparedStatement made statement reuse failed in some cases, as the closing and caching of the statement were not performed correctly."
[12 Oct 2024 0:38]
Daniel So
Posted by developer: Updated the changelog entry to the following: "Setting closeOnCompletion() on a PreparedStatement made statement reuse fail in some cases, as the closing and caching of the statement were not performed correctly."