kfirst opened a new issue, #26726: URL: https://github.com/apache/shardingsphere/issues/26726
## Bug Report Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? 5.3.2 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC ### Expected behavior Holded Savepoints should be removed after connection commit. ### Actual behavior Holded Savepoints do not be removed. ### Reason analyze (If you can) In ConnectionManager#setSavepoint method, we call "ConnectionSavepointManager.getInstance().setSavepoint" method to hold the savepoint in ConnectionSavepointManager, but in ConnectionManager#commit method, we do not call "ConnectionSavepointManager.getInstance().transactionFinished" to remove the holded savepoints. This causes memory leak. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. ### Example codes for reproduce this issue (such as a github link). -- 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]
