-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When shutting down after 4.1.1, an exception occurs while unregistering #4275
Comments
Same issue, attached some logs which may help diagnose the problem.
|
I face the same issue |
Same issue for me |
Hi @OlgaMaciaszek, can you please revert the MR mentioned in the OP? I will try to come up with a better solution that does not have this problem. Thanks in advance. |
@heowc Thanks for reporting the issue. Will do @ZIRAKrezovic. |
Regression removed with 79a2eb8. |
harshgandhi-1999
added a commit
to harshgandhi-1999/springboot-microservices
that referenced
this issue
Apr 20, 2024
[Error]: 2024-04-17T18:23:20.796+05:30 ERROR 22000 --- [accounts] [ Thread-9] com.netflix.discovery.DiscoveryClient : DiscoveryClient_ACCOUNTS/LAPTOP-JO8AOE56:accounts:8080 - de-registration failedCannot execute request on any known server com.netflix.discovery.shared.transport.TransportException: Cannot execute request on any known server [Resolution]: - Issue is occurring in latest spring cloud version 2023.0.1 so changed it to 2023.0.0. - Check this for more details spring-cloud/spring-cloud-netflix#4275
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently uploaded the spring cloud version and started using spring-cloud-netflix 4.1.1.
Since then, whenever the application is deployed,
DiscoveryClient
is shut down and an exception is repeatedly reported indicating that deregistration failed.The problem I think occurred while fixing the problem below.
If I replace it with the new
EurekaClientHttpRequestFactorySupplier
it doesn't throw any exception.(Remove the code related to
AtomicReference<CloseableHttpClient>
)The question I am curious about here is is there a reason to manage
CloseableHttpClient
separately rather than Spring Bean?The text was updated successfully, but these errors were encountered: