[Development error record] The service has been offline, but it is shown in eureka that the service is still causing service startup registration failure

Problem Description

In the development of microservices, a service has been offline for a long time, but eureka shows that the service is still causing the service startup and registration failure. The startup failure log is as follows:

org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name 'eurekaAutoServiceRegistration': Singleton bean creation not allowed while singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)

root cause

eureka did not find that the service provider has gone offline

problem solved

Manually force offline service

curl -v -X DELETE 192.168.56.138:28761/eureka/apps/MY-CONSTRUCTION/101.10.10.17:28114

Guess you like

Origin blog.csdn.net/runewbie/article/details/109340918