SpringCloud中Client向Eureka注册中心注册服务成功后不久就Unregistering（Unregistering application 服务名 with eureka with）

在SpringCloud中Server端启动成功了，再去启动Client项目，可能会出现这样的问题，Console日志如下：

2022-06-22 16:04:41.990  INFO 14964 --- [           main] c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at : http://localhost:9001/
2022-06-22 16:04:42.560  INFO 14964 --- [           main] c.c.c.ConfigServicePropertySourceLocator : Located environment: name=config, profiles=[test], label=master, version=28afd1f94d37c7a7fc60e402dab302bb178fae5c, state=null
2022-06-22 16:04:42.560  INFO 14964 --- [           main] b.c.PropertySourceBootstrapConfiguration : Located property source: [BootstrapPropertySource {name='bootstrapProperties-configClient'}, BootstrapPropertySource {name='bootstrapProperties-https://gitee.com/llongtong/zeno-training-platform-config.git/file:C:\Users\SAMSUNG\AppData\Local\Temp\config-repo-7871456846147239475\config-test.yml'}]
2022-06-22 16:04:42.576  INFO 14964 --- [           main] com.zeno.ConfigClientTestApplication     : No active profile set, falling back to default profiles: default
2022-06-22 16:04:42.866  INFO 14964 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=788e2244-e364-3193-959b-c9162cfcdae6
2022-06-22 16:04:43.971  INFO 14964 --- [           main] DiscoveryClientOptionalArgsConfiguration : Eureka HTTP Client uses RestTemplate.
2022-06-22 16:04:44.845  WARN 14964 --- [           main] iguration$LoadBalancerCaffeineWarnLogger : Spring Cloud LoadBalancer is currently working with the default cache. You can switch to using Caffeine cache, by adding it and org.springframework.cache.caffeine.CaffeineCacheManager to the classpath.
2022-06-22 16:04:44.892  INFO 14964 --- [           main] o.s.c.n.eureka.InstanceInfoFactory       : Setting initial instance status as: STARTING
2022-06-22 16:04:44.923  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Initializing Eureka in region us-east-1
2022-06-22 16:04:44.923  INFO 14964 --- [           main] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2022-06-22 16:04:44.939  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Disable delta property : false
2022-06-22 16:04:44.939  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Single vip registry refresh property : null
2022-06-22 16:04:44.939  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Force full registry fetch : false
2022-06-22 16:04:44.939  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Application is null : false
2022-06-22 16:04:44.939  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Registered Applications size is zero : true
2022-06-22 16:04:44.939  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Application version is -1: true
2022-06-22 16:04:44.939  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Getting all instance registry info from the eureka server
2022-06-22 16:04:45.111  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : The response status is 200
2022-06-22 16:04:45.111  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Starting heartbeat executor: renew interval is: 30
2022-06-22 16:04:45.111  INFO 14964 --- [           main] c.n.discovery.InstanceInfoReplicator     : InstanceInfoReplicator onDemand update allowed rate per min is 4
2022-06-22 16:04:45.111  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Discovery Client initialized at timestamp 1655885085111 with initial instances count: 3
2022-06-22 16:04:45.111  INFO 14964 --- [           main] o.s.c.n.e.s.EurekaServiceRegistry        : Registering application CONFIG-CLIENT with eureka with status UP
2022-06-22 16:04:45.111  INFO 14964 --- [           main] com.netflix.discovery.DiscoveryClient    : Saw local status change event StatusChangeEvent [timestamp=1655885085111, current=UP, previous=STARTING]
2022-06-22 16:04:45.126  INFO 14964 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_CONFIG-CLIENT/LONGTONG.mshome.net:config-client:8453: registering service...
2022-06-22 16:04:45.126  INFO 14964 --- [           main] com.zeno.ConfigClientTestApplication     : Started ConfigClientTestApplication in 5.828 seconds (JVM running for 8.011)
2022-06-22 16:04:45.142  INFO 14964 --- [ionShutdownHook] o.s.c.n.e.s.EurekaServiceRegistry        : Unregistering application CONFIG-CLIENT with eureka with status DOWN
2022-06-22 16:04:45.142  INFO 14964 --- [ionShutdownHook] com.netflix.discovery.DiscoveryClient    : Saw local status change event StatusChangeEvent [timestamp=1655885085142, current=DOWN, previous=UP]
2022-06-22 16:04:45.142  INFO 14964 --- [ionShutdownHook] com.netflix.discovery.DiscoveryClient    : Shutting down DiscoveryClient ...
2022-06-22 16:04:45.173  INFO 14964 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_CONFIG-CLIENT/LONGTONG.mshome.net:config-client:8453 - registration status: 204
2022-06-22 16:04:45.173  INFO 14964 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_CONFIG-CLIENT/LONGTONG.mshome.net:config-client:8453: registering service...
2022-06-22 16:04:45.173  INFO 14964 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_CONFIG-CLIENT/LONGTONG.mshome.net:config-client:8453 - registration status: 204
2022-06-22 16:04:45.173  INFO 14964 --- [ionShutdownHook] com.netflix.discovery.DiscoveryClient    : Unregistering ...
2022-06-22 16:04:45.173  INFO 14964 --- [ionShutdownHook] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_CONFIG-CLIENT/LONGTONG.mshome.net:config-client:8453 - deregister  status: 200
2022-06-22 16:04:45.189  INFO 14964 --- [ionShutdownHook] com.netflix.discovery.DiscoveryClient    : Completed shut down of DiscoveryClientProcess finished with exit code 0

其中，出了问题的大概可以从这里排查。

前面显示注册成功了，现在立马又开始倒戈。这是由于可能SpringWeb依赖是继承父模块的，所以我们这个模块里没有写Web依赖。

<dependency><groupId>org.springframework.boot</groupId><artifactId>spring-boot-starter-web</artifactId>
</dependency>

在我们这个模块pom文件里加上web依赖就搞定了。

SpringCloud中Client向Eureka注册中心注册服务成功后不久就Unregistering（Unregistering application 服务名 with eureka with）相关推荐

注册中心—注册中心原理
在微服务架构中,注册中心是最核心的基础服务之一,本文将详细介绍下注册中心的组成部分和它们之前的关系. 目录一.注册中心原理二.注册中心功能三.常见的注册中心一.注册中心原理注册中心主要涉及到 ...
spring cloudAlibaba gateway网关报错，显示无法找到注册中心注册自己。
spring cloudAlibaba gateway网关报错,显示无法找到注册中心注册自己. 1.错误提示 2020-12-29 11:10:18.521 WARN 232 --- [freshEx ...
python 使用nacos 注册中心注册服务
python 使用nacos 注册中心注册服务最近一段时间要将自己写的flask 项目作为一个微服务,因为这边java 使用的nacos 为注册中心. 所有便简单实现了一下 . https:// ...
Consul注册中心注册的服务总是红叉 (All service checks failing)
Consul注册中心注册的服务总是红叉 (All service checks failing) Consul注册中心注册的服务总是红叉 (All service checks failing) 因为 ...
spring-cloud开发微服务笔记（二）：高可用Eureka注册中心的搭建与RestTemplate和Fengin客户端调用微服务示例
引言:这一篇博客是将上一篇spring-cloud-eureka-server的单机模式改为集群模式,体现eureka的高可用特性.生产环境无论是Eureka注册中心还是Client客户端大多是部署在 ...
通过Maven将一个dubbo服务打包成可执行的jar包，并向注册中心注册服务
1.向pom.xml里面添加如下代码: dubbo-Service${project.build.directory}/classessrc/main/resourcestrue**/*.prope ...
java项目（注册和登录（成功后查看商品的信息））
文章目录声明第一步: 第二步: 第三步: 第四步: 第五步第六步: 第七步: 声明题目:实现登录和注册功能登录成功后可以查看所有商品的信息(商品名称,价格,销量) 第一步: package ...
禁止本地服务dubbo、nacos服务法宣向注册中心注册
dubbo.registry.register=false spring.cloud.nacos.discovery.register-enabled=true
计算机和建筑学薪资待遇区别,工科中薪资待遇最高、女生最多、毕业后竞争最激烈的前两名专业！...
现代社会工科是着重培养应用型人才,随着我国社会经济进入高质量的发展"高速路",对于高质量的工科人才需求正在稳步提升,待遇好.好就业是工科专业最大的优点所在.正因为此,工科类专业都受 ...

SpringCloud中Client向Eureka注册中心注册服务成功后不久就Unregistering（Unregistering application 服务名 with eureka with）

SpringCloud中Client向Eureka注册中心注册服务成功后不久就Unregistering（Unregistering application 服务名 with eureka with）相关推荐

最新文章

热门文章