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?
I recently uploaded the spring cloud version and started using spring-cloud-netflix 4.1.1.
Since then, whenever the application is deployed,
DiscoveryClientis 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
EurekaClientHttpRequestFactorySupplierit 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
CloseableHttpClientseparately rather than Spring Bean?