fix close_wait and tomcat connection keeps growing #726
+3
−0
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.
Motivation and Context
Reproduction Scenario:
Perform stress testing at 120 TPS.
MCP client/server environment: 4 cores, 8 GB memory.
Create an MCP client, invoke methods, then close the client.
Issue:
A large number of CLOSE_WAIT connections appear on the Tomcat side. Meanwhile, the number of Tomcat connections keeps increasing. After observation, neither the CLOSE_WAIT states nor the connections are being released.
CLOSE_WAIT
Tomcat Connection
How Has This Been Tested?
Breaking Changes
benchmark test
Types of changes
Checklist
Additional context