-
Notifications
You must be signed in to change notification settings - Fork 540
Open
Labels
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