-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
DefaultEurekaClientHttpRequestFactorySupplier HttpClient is not closed #4062
Comments
Hello, @Ive4 thanks for submitting this. I'm not sure what you mean. In the |
Sorry, I didn't make it clear. |
Hello, @Ive4 if I understand correctly, the issue concerns the |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Hi @OlgaMaciaszek ,
This bug is related to Line 203 in 27ac337
In case of exception here: I'll try to explain the issue, let me know if you still want complete mvce. Line 103 in 27ac337
so in case of shutdown, currentEurekaClient shutdown don't closes connections: Line 203 in 27ac337
as @Ive4 said, only Full GC closes the opened connections. possible solution will be trying to close the HttpClient:
|
Describe the bug
spring cloud 2021.0.0
Eureka Client has a bug, the bug is that every time the heartbeat and request Eureka Server will create a new HttpClient, but this new HttpClient will not be manually closed, only when the FullGC will be cleaned up, so it leads to the problem of too much TCP CLOSE_WAIT.
Sample
The solution is to provide a shared HttpClient, rather than re-creating a new one for each request.
The text was updated successfully, but these errors were encountered: