branch-3.1: [fix](jdbc) Fix JNI global reference leak in JdbcConnector close #58574 #58752
+54
−15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…8574) ## Problem JNI Global References may not be deleted when `JdbcConnector::close()` fails midway due to early returns from `RETURN_IF_ERROR` macros. This prevents Java GC from collecting `BaseJdbcExecutor` and its associated `ResultSet` objects, causing old generation heap to grow to 99%+. ## Solution - C++: Always delete all three Global References regardless of Java close() failure - Java: Always clear member variable references (`resultSet`, `stmt`, `conn`) in finally block
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
|
run buildall |
morrySnow
approved these changes
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-picked from #58574