Nacos之 SpringCloud alibaba 问题点：本地服务注册不到Nacos里,但是Idea的application 可以启动正常，解决服务注册不进去的问题---已解决

置顶 已于 2022-05-31 10:59:34 修改
阅读量2.2w 收藏 3
点赞数 4
文章标签： java
于 2021-02-25 20:48:27 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_43618209/article/details/114105571
版权

1.首先提供IDEA的控制台报错信息：如下

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::        (v2.2.2.RELEASE)

2021-02-25 19:48:37.791  INFO 2972 --- [           main] com.george.springcloud.PaymentMain9001   : No active profile set, falling back to default profiles: default
2021-02-25 19:48:38.311  WARN 2972 --- [           main] o.s.boot.actuate.endpoint.EndpointId     : Endpoint ID 'nacos-discovery' contains invalid characters, please migrate to a valid format.
2021-02-25 19:48:38.491  WARN 2972 --- [           main] o.s.boot.actuate.endpoint.EndpointId     : Endpoint ID 'service-registry' contains invalid characters, please migrate to a valid format.
2021-02-25 19:48:38.611  INFO 2972 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=d12ded74-3dde-36c6-bbb6-e87f1dca1ffc
2021-02-25 19:48:38.920  INFO 2972 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 9001 (http)
2021-02-25 19:48:38.930  INFO 2972 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2021-02-25 19:48:38.930  INFO 2972 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.29]
2021-02-25 19:48:39.120  INFO 2972 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2021-02-25 19:48:39.120  INFO 2972 --- [           main] o.s.web.context.ContextLoader            : Root WebApplicationContext: initialization completed in 1309 ms
2021-02-25 19:48:40.510  WARN 2972 --- [           main] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2021-02-25 19:48:40.510  INFO 2972 --- [           main] c.n.c.sources.URLConfigurationSource     : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2021-02-25 19:48:40.520  WARN 2972 --- [           main] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2021-02-25 19:48:40.520  INFO 2972 --- [           main] c.n.c.sources.URLConfigurationSource     : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2021-02-25 19:48:40.650  INFO 2972 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
2021-02-25 19:48:40.879  INFO 2972 --- [           main] o.s.s.c.ThreadPoolTaskScheduler          : Initializing ExecutorService
2021-02-25 19:48:42.908  INFO 2972 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 18 endpoint(s) beneath base path '/actuator'
2021-02-25 19:48:42.968  INFO 2972 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 9001 (http) with context path ''
2021-02-25 19:48:43.068 ERROR 2972 --- [           main] c.a.c.n.registry.NacosServiceRegistry    : nacos registry, nacos-payment-provider register failed...NacosRegistration{nacosDiscoveryProperties=NacosDiscoveryProperties{serverAddr='localhost:8848', endpoint='', namespace='', watchDelay=30000, logName='', service='nacos-payment-provider', weight=1.0, clusterName='DEFAULT', namingLoadCacheAtStart='false', metadata={preserved.register.source=SPRING_CLOUD}, registerEnabled=true, ip='192.168.1.10', networkInterface='', port=9001, secure=false, accessKey='', secretKey=''}},

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance after all servers([localhost:8848]) tried: failed to req API:localhost:8848/nacos/v1/ns/instance. code:401 msg: <html><body><h1>Whitelabel Error Page</h1><p>This application has no explicit mapping for /error, so you are seeing this as a fallback.</p><div id='created'>Thu Feb 25 19:48:43 CST 2021</div><div>There was an unexpected error (type=Unauthorized, status=401).</div><div>Unauthorized</div></body></html>
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:464) ~[nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:386) ~[nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.registerService(NamingProxy.java:188) ~[nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.NacosNamingService.registerInstance(NacosNamingService.java:205) ~[nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.NacosNamingService.registerInstance(NacosNamingService.java:184) ~[nacos-client-1.1.1.jar:na]
	at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.register(NacosServiceRegistry.java:61) ~[spring-cloud-alibaba-nacos-discovery-2.1.0.RELEASE.jar:2.1.0.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.register(AbstractAutoServiceRegistration.java:239) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at com.alibaba.cloud.nacos.registry.NacosAutoServiceRegistration.register(NacosAutoServiceRegistration.java:74) [spring-cloud-alibaba-nacos-discovery-2.1.0.RELEASE.jar:2.1.0.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.start(AbstractAutoServiceRegistration.java:138) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.bind(AbstractAutoServiceRegistration.java:101) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:88) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:47) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:403) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:360) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:165) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at com.george.springcloud.PaymentMain9001.main(PaymentMain9001.java:16) [classes/:na]

2021-02-25 19:48:44.058  INFO 2972 --- [           main] com.george.springcloud.PaymentMain9001   : Started PaymentMain9001 in 10.381 seconds (JVM running for 12.133)

2.本地用户Nacos的naming 文本信息 text

2021-02-25 19:48:40.430 INFO [main :c.a.n.c.naming] initializer namespace from System Property :null
2021-02-25 19:48:40.430 INFO [main :c.a.n.c.naming] initializer namespace from System Environment :null
2021-02-25 19:48:40.430 INFO [main :c.a.n.c.naming] initializer namespace from System Property :null
2021-02-25 19:48:42.978 INFO [main :c.a.n.c.naming] [BEAT] adding beat: {"cluster":"DEFAULT","ip":"192.168.1.10","metadata":{"preserved.register.source":"SPRING_CLOUD"},"period":5000,"port":9001,"scheduled":false,"serviceName":"DEFAULT_GROUP@@nacos-payment-provider","stopped":false,"weight":1.0} to beat map.
2021-02-25 19:48:43.048 INFO [main :c.a.n.c.naming] [REGISTER-SERVICE] public registering service DEFAULT_GROUP@@nacos-payment-provider with instance: {"clusterName":"DEFAULT","enabled":true,"ephemeral":true,"healthy":true,"instanceHeartBeatInterval":5000,"instanceHeartBeatTimeOut":15000,"ip":"192.168.1.10","ipDeleteTimeout":30000,"metadata":{"preserved.register.source":"SPRING_CLOUD"},"port":9001,"weight":1.0}
2021-02-25 19:48:43.068 ERROR [com.alibaba.nacos.naming.beat.sender:c.a.n.c.naming] request localhost:8848 failed.
com.alibaba.nacos.api.exception.NacosException: failed to req API:localhost:8848/nacos/v1/ns/instance/beat. code:401 msg: <html><body><h1>Whitelabel Error Page</h1><p>This application has no explicit mapping for /error, so you are seeing this as a fallback.</p><div id='created'>Thu Feb 25 19:48:43 CST 2021</div><div>There was an unexpected error (type=Unauthorized, status=401).</div><div>Unauthorized</div></body></html>
	at com.alibaba.nacos.client.naming.net.NamingProxy.callServer(NamingProxy.java:424) [nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:451) [nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:386) [nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.sendBeat(NamingProxy.java:309) [nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.beat.BeatReactor$BeatTask.run(BeatReactor.java:92) [nacos-client-1.1.1.jar:na]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_131]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_131]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_131]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_131]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_131]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_131]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]
2021-02-25 19:48:43.068 ERROR [main :c.a.n.c.naming] request localhost:8848 failed.
com.alibaba.nacos.api.exception.NacosException: failed to req API:localhost:8848/nacos/v1/ns/instance. code:401 msg: <html><body><h1>Whitelabel Error Page</h1><p>This application has no explicit mapping for /error, so you are seeing this as a fallback.</p><div id='created'>Thu Feb 25 19:48:43 CST 2021</div><div>There was an unexpected error (type=Unauthorized, status=401).</div><div>Unauthorized</div></body></html>
	at com.alibaba.nacos.client.naming.net.NamingProxy.callServer(NamingProxy.java:424) [nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:451) [nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:386) [nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.registerService(NamingProxy.java:188) [nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.NacosNamingService.registerInstance(NacosNamingService.java:205) [nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.NacosNamingService.registerInstance(NacosNamingService.java:184) [nacos-client-1.1.1.jar:na]
	at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.register(NacosServiceRegistry.java:61) [spring-cloud-alibaba-nacos-discovery-2.1.0.RELEASE.jar:2.1.0.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.register(AbstractAutoServiceRegistration.java:239) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at com.alibaba.cloud.nacos.registry.NacosAutoServiceRegistration.register(NacosAutoServiceRegistration.java:74) [spring-cloud-alibaba-nacos-discovery-2.1.0.RELEASE.jar:2.1.0.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.start(AbstractAutoServiceRegistration.java:138) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.bind(AbstractAutoServiceRegistration.java:101) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:88) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:47) [spring-cloud-commons-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:403) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:360) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:165) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) [spring-context-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.2.2.RELEASE.jar:2.2.2.RELEASE]
	at com.george.springcloud.PaymentMain9001.main(PaymentMain9001.java:16) [classes/:na]
2021-02-25 19:48:43.068 ERROR [com.alibaba.nacos.naming.beat.sender:c.a.n.c.naming] [CLIENT-BEAT] failed to send beat: {"cluster":"DEFAULT","ip":"192.168.1.10","metadata":{"preserved.register.source":"SPRING_CLOUD"},"period":5000,"port":9001,"scheduled":false,"serviceName":"DEFAULT_GROUP@@nacos-payment-provider","stopped":false,"weight":1.0}
java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance/beat after all servers([localhost:8848]) tried: failed to req API:localhost:8848/nacos/v1/ns/instance/beat. code:401 msg: <html><body><h1>Whitelabel Error Page</h1><p>This application has no explicit mapping for /error, so you are seeing this as a fallback.</p><div id='created'>Thu Feb 25 19:48:43 CST 2021</div><div>There was an unexpected error (type=Unauthorized, status=401).</div><div>Unauthorized</div></body></html>
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:464) ~[nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:386) ~[nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.sendBeat(NamingProxy.java:309) ~[nacos-client-1.1.1.jar:na]
	at com.alibaba.nacos.client.naming.beat.BeatReactor$BeatTask.run(BeatReactor.java:92) [nacos-client-1.1.1.jar:na]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_131]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_131]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_131]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_131]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_131]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_131]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]

相关YML

server:
  port: 9001

spring:
  application:
    name: nacos-payment-provider
  cloud:
    nacos:
      discovery:
        server-addr: localhost:8848 #配置nacos地址

management:
  endpoints:
    web:
      exposure:
        include: "*"

在这里插入图片描述

在这里插入图片描述
在这里插入图片描述

上图 可证 本地Nacos 成功启动；

解决方法： 官网明确给出2021年2月5号Nacos的稳定客户端版本,替换本地原先更新的1.1.4版本 用2.0.0-BATA版本 ，重新安装Nacos-server-2.0.0-BATA

github下载地址：https://github.com/alibaba/nacos/releases/tag/2.0.0-BETA
重新安装即可;


 cmd下操作，启动Nacos, 出现 DB is null 该描述性 错误的，

解决该问题的方式：
由于该新下载的包为内置配置 模式是 cluster ，
我个人玩的是本地 单机版 所以改成 standalone 即可；
standalones 也是会报上述错误；

在bin目录下，找到startup.cmd  用文档编辑方式打开，即可看到，修改即可。

如果您需要配置集群 cluster ，需要添加本地 内置数据库，该本分内容后续更新。

改完上述内容，重新启动Nacos,在启动配置好的9001 需要注册进Nacos的nacos-payment-provider服务即可。

在这里插入图片描述
![在这里插入图片描述](https://img-blog.csdnimg.cn/20210226132930645.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3dlaXhpbl80MzYxODIwOQ==,size_16,color_FFFFFF,t_70
看到该服务 已经注册进来，问题已解决。

感谢大家关注，谢谢大家。

　Admin
关注
  • 4
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 2
    评论
SpringCloud War 包部署导致服务未正常注册到 Nacos 问题
空夜's Blog
12-30 4430
SpringCloud 微服务项目使用 War 包部署到 Nacos，服务注册失败，没有错误日志，本节介绍了该问题的原因和解决办法。
nacos-spring-cloud-example.zip
08-23
3. **创建Spring Cloud项目**：在IDEA中新建一个Spring Boot项目，加入Spring Cloud和Nacos的相关依赖，如`spring-cloud-starter-alibaba-nacos-discovery`等。 4. **配置Nacos**：在项目的application.yml或...
图文结合教你SpringBoot中初始化Tomcat以及Tomcat运行原理
weixin_41816847的博客
06-29 2732
SpringBoot中是如何初始化Tomcat 的 前言 ​ SpringBoot的创造简化了我们创建项目和运行项目的工作。我们不必再像SpringMVC时代那样，将项目先打包成jar包，然后放入Tomcat中再启动。我们可以忽略打包的操作和tomat的配置问题，编写完代码后直接启动项目即可。这一切都得益于SpringBoot的内置容器的实现。那么，SpringBoot具体是如何为我们完成了初始化Tomcat 的这一系列的操作的呢？下面我将以第一人称的学习源码视角带领大家来一起快乐分析SpringBoot的
生产问题排查：springboot项目启动时注册nacos失败或运行时从nacos闪退
最新发布
秃了也弱了
06-04 856
需要注意的是，当Pod被控制器（如Deployment、StatefulSet等）管理时，即使Pod未明确指定重启策略，控制器也会根据自身逻辑控制Pod副本的重启行为。这是默认的重启策略。生产项目是用k8s部署的，最近经常遇到启动时注册不到nacos（查找nacos的host地址找不到），或者运行的好好的，突然也连不上nacos了（同样是查找nacos的host地址找不到）。好在如果发生了这个异常，就会中断springboot项目的启动，用健康检查就非常的合适，此时健康检查的接口都调用不到。
电脑太卡怎么办？
xiyangyang8110的博客
10-21 501
最近用了之前后端开发人员的电脑，发现特别慢，打开的网页也卡，最后排查是因为oracle后台服务一直开着，把服务自动改成手动好了（控制面板–系统和安全–管理工具–服务–把一些不用的服务自动改手动） ...
nacos 启动_【Nacos源码之配置管理 一】阅读源码第一步,本地启动Nacos
weixin_39805387的博客
12-05 703
前言在我们去阅读Nacos源码之前,我们得先了解Nacos是干嘛的,以及怎么用,这样有利于我们更容易去理解源码;查看Nacos的官方文档,我们知道Naocs主要有以下特性:配置中心服务注册与发现...Nacos有给我们提供管理界面,用来方便配置数据;我们先把整个Nacos源码克隆下来,本地启动;熟悉一下如何使用它启动Nacos项目1.克隆Nacos源码git clone https://githu...
本地服务注册不到测试环境的nacos注册中心
m0_58875823的博客
11-11 1925
本地服务注册不到测试环境的nacos注册中心
服务没有注册到nacos的原因分析
qq_36749924的博客
09-11 7330
服务没有注册到nacos的原因分析 因为没有加上版本号，导致不能注册。 <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId> <version>0.2.1.RELEASE<
SpringCloud项目中使用Nacos作为注册中心
03-16
在SpringCloud项目中，Nacos作为一个重要的组件，常被用作服务发现和配置管理的注册中心。本项目中，我们采用Nacos-server-1.3.2版本进行部署，并将其与IntelliJ IDEA（IDEA）环境下的SpringBoot应用集成，以实现...
Spring Cloud alibaba 环境搭建代码
11-18
Spring Cloud Alibaba 是一套基于 Spring Boot 和 Spring Cloud 的微服务架构解决方案，它提供了众多的企业级中间件，如分布式配置中心、注册中心、API 网关、消息队列、限流降级、熔断器等。本环境搭建代码将指导你...
SpringCloudAlibaba二整合Nacos
10-19
在分布式系统中，Spring Cloud Alibaba 是一套微服务解决方案，它为开发者提供了在分布式系统的配置管理、服务发现、断路器、智能路由、微代理、控制总线、分布式会话、集群状态等一系列功能。Nacos 是 Spring Cloud...
Spring Cloud alibaba项目搭建及配置详细步骤
10-17
Spring Cloud Alibaba是阿里巴巴提供的微服务解决方案，它将一系列开源组件集成到Spring Cloud生态系统中，以帮助开发者构建分布式系统。在本教程中，我们将探讨如何搭建一个基于Spring Cloud Alibaba的项目并进行...
springcloud项目启动以后没注册到nacos
qq_44624290的博客
05-03 4574
根本原因：没有依赖 问题过程 项目启动成功之后的截图 可以看到nacos只有网关，并没有flight-query这个服务 <nacos.discovery.version>2.2.3.RELEASE</nacos.discovery.version> <!--nacos服务注册依赖--> <dependency> <groupId>com.alibaba.cloud</..
Nacos本地启动不注册服务
果酱 の 博客
06-28 5488
Nacos本地启动不注册服务解决办法
SpringCloud - 如何本地调试不会注册到线上环境（Nacos）？
牧码的博客
04-03 1044
SpringCloud - 如何本地调试不会注册到线上环境（Nacos）？
springcloud项目启动成功之后没能注册到nacos上。
ZhangGuoLonglong的博客
12-30 4043
springcloud项目启动成功之后没能注册到nacos上。 项目启动成功之后的截图 可以看到服务启动之后在nacos上没有出现zgl-message服务 原因是没有添加依赖 <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> <versio
Spring boot项目打包war部署外部tomcat无法注册到Nacos
丙火的博客
07-28 508
现象 Spring boot 或者 Spring cloud 项目，如果用默认的打包jar, 使用内嵌的tomcat 启动，可以正常注册到Nacos 注册中心。 如果打包为war,部署到外部tomcat, 调用正常，消费者可以调用到 生产者服务，但是Nacos 后台的服务列表里没有显示。很诡异。。。 分析 查看源码，需从nacos的注册类找起，查找后发现，nacos注册类NacosAutoServiceRegistration继承了Spring Cloud中AbstractAutoServiceReg
Spring Cloud微服务在Windows本地开发时禁用Nacos注册中心注册
码到三十五
03-09 1757
通过简单地在启动类中编写条件逻辑，我们可以实现在Windows本地开发环境下禁用Nacos服务注册，而在Linux服务器环境下自动启用注册功能。然而，在开发过程中，开发者可能希望在本地机器上进行测试，而不希望服务自动注册到Nacos注册中心，以免影响到测试环境。这样配置后，您就可以方便地在本地进行自测，而不用担心对测试环境造成干扰。本文将介绍如何在Spring Cloud微服务架构中，实现在Windows本地开发环境下禁用服务自动注册到Nacos注册中心，而在Linux服务器环境下则自动启用注册功能。
SpringCloud微服务本地不要注册到nacos或eureka
yuguang的博客
02-27 3358
【代码】SpringCloud微服务不要注册到注册中心。
idea在springboot2.7.12下nacos创建服务端与客户端，实现服务的注册与发现
06-02
下面是在 Spring Boot 2.7.12 中使用 Nacos 实现服务注册与发现的步骤： 1. 引入 Nacos 相关依赖 在 pom.xml 文件中添加以下依赖： ```xml <dependency> <groupId>com.alibaba.cloud</groupId> <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId> <version>2.2.6.RELEASE</version> </dependency> ``` 2. 配置 Nacos 服务器地址 在 application.yml 文件中添加以下配置： ```yaml spring: cloud: nacos: discovery: server-addr: localhost:8848 ``` 其中，server-addr 指定了 Nacos 服务器的地址。 3. 创建服务提供者 在 Spring Boot 应用中，可以通过添加 @EnableDiscoveryClient 注解来启用服务注册与发现功能。同时，需要在服务提供者的代码中添加 @RestController 和 @GetMapping 注解，定义一个简单的 REST 接口，用于测试服务的注册与发现。 ```java @RestController public class HelloController { @GetMapping("/hello") public String hello() { return "Hello, Nacos!"; } } ``` 4. 创建服务消费者 在服务消费者的代码中，同样需要添加 @EnableDiscoveryClient 注解来启用服务注册与发现功能。同时，需要使用 @Autowired 注解注入一个 RestTemplate 对象，并使用 @LoadBalanced 注解对其进行修饰，以支持负载均衡。具体代码如下： ```java @RestController public class ConsumerController { @Autowired @LoadBalanced private RestTemplate restTemplate; @GetMapping("/hello") public String hello() { String url = "http://service-provider/hello"; return restTemplate.getForObject(url, String.class); } } ``` 其中，service-provider 是服务提供者的应用名称，可以通过 @GetMapping 注解中的 URL 地址进行访问。 5. 运行应用 启动服务提供者和服务消费者应用后，可以通过 Nacos 控制台进行服务的注册与发现，或者直接通过服务消费者的接口进行访问。 以上就是在 Spring Boot 2.7.12 中使用 Nacos 实现服务注册与发现的简单示例，希望对你有所帮助。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值