spring-cloud / spring-cloud/spring-cloud-consul
ESTABLISHED and thread leaks
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 822
- Forks
- 539
- Avg merge
- 9h 31m
- Merged PRs (30d)
- 7
Description
Describe the bug
This is my version number。
SpringBoot 3.4.1
SpringCloud 2024.0.0
SpringCLoud Consul 4.2.0
The Consul Agent was used. When I used the above version, I found that there were long-term ESTABLISHED threads occupying port 8500 that had not been destroyed for a long time.
After investigation, it was found that it would increase as the number of HTTP threads grew and would not be destroyed.
When I was using the final version of JDK8, we found that it was the same. Then I ruled out that SpringCloud would cause thread leaks.
Even now, when we use the above version, it still occurs. May I ask if there are any references for us to avoid this phenomenon?
This is ESTABLISHED to Consul Agent 8500
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is identified. Start by reproducing the reported long-lived ESTABLISHED connections to Consul Agent port 8500 with the listed Spring Boot, Spring Cloud, and JDK versions; done means identifying whether the project causes the connections and documenting a verified way to avoid or resolve the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100