linghengqian opened a new pull request, #34498:
URL: https://github.com/apache/shardingsphere/pull/34498
Fixes #34418 .
Changes proposed in this pull request:
- Alleviate the connection leak caused by Seata Client throwing exceptions
in `CONNECTION_STRICTLY` connection mode.
- This is basically a variation of #34463 . More investigation is at
https://github.com/apache/shardingsphere/issues/34418#issuecomment-2613944063
and
https://shardingsphere.apache.org/document/current/en/reference/sharding/execute/
.
- No issue has ever provided a reproducible unit test. Currently all
relevant unit tests actively exploit the connection leak bug on Seata Client
`2.2.0`.
---
Before committing this PR, I'm sure that I have checked the following
options:
- [x] My code follows the [code of
conduct](https://shardingsphere.apache.org/community/en/involved/conduct/code/)
of this project.
- [x] I have self-reviewed the commit code.
- [x] I have (or in comment I request) added corresponding labels for the
pull request.
- [x] I have passed maven check locally : `./mvnw clean install -B -T1C
-Dmaven.javadoc.skip -Dmaven.jacoco.skip -e`.
- [ ] I have made corresponding changes to the documentation.
- [x] I have added corresponding unit tests for my changes.
- [x] I have updated the Release Notes of the current development version.
For more details, see [Update Release
Note](https://shardingsphere.apache.org/community/en/involved/contribute/contributor/)
--
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: notifications-unsubscr...@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
