nacos-group / nacos-examples Goto Github PK

nacos-config-spring-boot-starter版本0.2.3和0.2.3的均有以下错误，0.2.2和0.2.1是OK的

java.lang.UnsupportedOperationException: Parsing is not yet supported for this type profile : test
at com.alibaba.nacos.spring.util.ConfigParseUtils.toProperties(ConfigParseUtils.java:100) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.util.ConfigParseUtils.toProperties(ConfigParseUtils.java:128) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.util.NacosUtils.toProperties(NacosUtils.java:444) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.core.env.NacosPropertySource.(NacosPropertySource.java:67) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.core.env.AbstractNacosPropertySourceBuilder.doBuild(AbstractNacosPropertySourceBuilder.java:195) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.core.env.AbstractNacosPropertySourceBuilder.build(AbstractNacosPropertySourceBuilder.java:118) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.core.env.NacosPropertySourcePostProcessor.buildNacosPropertySources(NacosPropertySourcePostProcessor.java:151) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.core.env.NacosPropertySourcePostProcessor.processPropertySource(NacosPropertySourcePostProcessor.java:133) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.core.env.NacosPropertySourcePostProcessor.postProcessBeanFactory(NacosPropertySourcePostProcessor.java:118) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.util.NacosBeanUtils.invokeNacosPropertySourcePostProcessor(NacosBeanUtils.java:426) ~[nacos-spring-context-0.3.4.jar:na]
at com.alibaba.nacos.spring.context.annotation.config.NacosConfigBeanDefinitionRegistrar.registerBeanDefinitions(NacosConfigBeanDefinitionRegistrar.java:73) ~[nacos-spring-context-0.3.4.jar:na]
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.lambda$loadBeanDefinitionsFromRegistrars$1(ConfigurationClassBeanDefinitionReader.java:364) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at java.util.LinkedHashMap.forEach(LinkedHashMap.java:684) ~[na:1.8.0_191]
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsFromRegistrars(ConfigurationClassBeanDefinitionReader.java:363) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:145) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:117) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:327) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:232) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:275) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:95) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:691) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:528) ~[spring-context-5.1.2.RELEASE.jar:5.1.2.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140) ~[spring-boot-2.1.0.RELEASE.jar:2.1.0.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775) [spring-boot-2.1.0.RELEASE.jar:2.1.0.RELEASE]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) [spring-boot-2.1.0.RELEASE.jar:2.1.0.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:316) [spring-boot-2.1.0.RELEASE.jar:2.1.0.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260) [spring-boot-2.1.0.RELEASE.jar:2.1.0.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248) [spring-boot-2.1.0.RELEASE.jar:2.1.0.RELEASE]
at com.softbankrobotics.springboot.demo.StartApplication.main(StartApplication.java:33) [classes/:na]

请教一下，nacos存储方式yml或者properties文件格式，list或者map数据类型怎么读取啊

场景:
@configuration
@EnableNacosConfig(globalProperties = @NacosProperties(serverAddr ="${nacos.addr:localhost}"))
@NacosPropertySources({
@NacosPropertySource(dataId = “datasource”, autoRefreshed = true,
groupId = "${nacos.group:DEFAULT_GROUP}")
public class NacosConfiguration { }
解析@NacosPropertySource属性值在AbstractNacosPropertySourceBuilder的doBind方法，
groupId = NacosUtils.readFromEnvironment(groupId, environment);
在读取属性时，没有将默认值分开

求助，springcloud中注册中心替换成nacos，用zuul代理。在zuul微服务启动之后，新注册的微服务能在nacos服务列表查看到，但通过zuul无法访问，非得zuul重启后才能访问新注册的服务。。。这是缺少什么配置吗

已经刷新了，但是拿到的值还是旧的

spring-cloud-starter-alibaba-nacos用的0.2.1.RELEASE版本,
spring-cloud-dependencies用的Finchley.RELEASE版本.
当spring-boot-dependencies使用2.1.0及以上版本的时候, nacos console未发现服务
, 且更改配置文件后@RefreshScope没有触发自动更新.
尝试了一下, 2.0.4至2.0.8版本中没有这个问题

类似这样的配置，如何获取

spring-cloud-starter-alibaba-nacos-config（版本：0.2.0.BUILD-SNAPSHOT）从哪里下载

Description

Add the example of Selector in Nacos 2.x.

版本：
java 1.8.0
spring-boot 2.1.7
nacos 0.2.1

https://github.com/nacos-group/nacos-examples/blob/master/nacos-spring-boot-example/nacos-spring-boot-discovery-example/src/main/java/com/alibaba/nacos/example/spring/boot/NacosDiscoveryApplication.java

最后发现 endpoint 变量为空

java.io.IOException: Error while requesting: http://null/vipserver/serverlist'. Server returned: 500
	at com.alibaba.nacos.client.naming.net.NamingProxy.getServerListFromEndpoint(NamingProxy.java:102)
	at com.alibaba.nacos.client.naming.net.NamingProxy.refreshSrvIfNeed(NamingProxy.java:135)
	at com.alibaba.nacos.client.naming.net.NamingProxy.access$000(NamingProxy.java:39)
	at com.alibaba.nacos.client.naming.net.NamingProxy$2.run(NamingProxy.java:83)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

拿到了Instance成功了,怎么用, 不然拿到了也没用

    @RequestMapping(value = "/get", method = GET)
    @ResponseBody
    public String get(@RequestParam String serviceName) throws NacosException {
        List<Instance> ret= namingService.getAllInstances(serviceName);
        Instance nacosServer=(Instance) ret.get(0);
        ISysClient sysClient= (ISysClient)  nacosServer; //这里报错误了
        R<String> retData=sysClient.getDeptIds(11L,"dd");
        System.out.printf("ret="+retData);
        return "";
    }


报错:
java.lang.ClassCastException: com.alibaba.nacos.api.naming.pojo.Instance cannot be cast to com.alibaba.nacos.example.spring.controller.ISysClient
	at com.alibaba.nacos.example.spring.controller.DiscoveryController.get(DiscoveryController.java:31)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:743)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:672)
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:82)
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:933)
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:842)

NacosPropertySource注解只在默认的public namespace下生效，切换到自定义的namespace不生效

springboot example

@RefreshScope和@configuration组合，虽然@value下的值已经变了，但Bean并没有重新加载，请问怎么解决

nacos-spring-boot-discovery-example启动后无法将服务注册到 Nacos

参考https://github.com/nacos-group/nacos-examples/tree/master/nacos-spring-cloud-example 例子， 采用
Spring boot 2.1.7.RELEASE
Spring Cloud Greenwich
Spring Cloud Alibaba Version 0.9.0.RELEASE
nacos-client 1.1.3
项目启动成功，在nacos server上也注册成功，
但是在代码controller层 使用@NacosInjected 注入Nacos 的NamingService实例以及ConfigService都为null ，请问是什么原因导致？？

Hello，大家好
例子中的springCloudAlibaba 版本比较老，可以更新下吗，这个任务交给我

问题描述

1. 没有并发
2. 没有大文件传输
3. 网络会不稳定

当前的情况

过一两天就会断开连接，需要手动重启java服务，nacos服务一直正常运行，也没有日志

期望

可以配置，即使断开了，等正常的时候自动注册上去，就不用每次都重启应用了。

服务启动后注册成功，过一段时间，java应用就断开，在注册中心也看不到注册的服务了，然后必须重启java应用才会重新注册，java应用日志报错如下：

[mogu-admin:10.244.3.112:8080] [,] 2021-06-05 04:10:48.780 ERROR 1 [com.alibaba.nacos.client.Worker.longPolling.fixed-nacos.gulimall.svc.cluster.local_8848] com.alibaba.nacos.client.config.impl.ClientWorker [fixed-nacos.gulimall.svc.cluster.local_8848] [check-update] get changed dataId exception

java.net.UnknownHostException: nacos.gulimall.svc.cluster.local
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
	at sun.net.www.http.HttpClient.New(HttpClient.java:339)
	at sun.net.www.http.HttpClient.New(HttpClient.java:357)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1334)
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1309)
	at com.alibaba.nacos.common.http.client.request.JdkHttpClientRequest.execute(JdkHttpClientRequest.java:106)
	at com.alibaba.nacos.common.http.client.InterceptingHttpClientRequest.execute(InterceptingHttpClientRequest.java:53)
	at com.alibaba.nacos.common.http.client.NacosRestTemplate.execute(NacosRestTemplate.java:482)
	at com.alibaba.nacos.common.http.client.NacosRestTemplate.postForm(NacosRestTemplate.java:407)
	at com.alibaba.nacos.client.config.http.ServerHttpAgent.httpPost(ServerHttpAgent.java:155)
	at com.alibaba.nacos.client.config.http.MetricsHttpAgent.httpPost(MetricsHttpAgent.java:68)
	at com.alibaba.nacos.client.config.impl.ClientWorker.checkUpdateConfigStr(ClientWorker.java:441)
	at com.alibaba.nacos.client.config.impl.ClientWorker.checkUpdateDataIds(ClientWorker.java:408)
	at com.alibaba.nacos.client.config.impl.ClientWorker$LongPollingRunnable.run(ClientWorker.java:596)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

环境

spring配置

spring:
  application:
    name: mogu_web
  cloud:
    nacos:
      discovery:
        server-addr: ${nacos_config_discovery}
        heart-beat-timeout: 30000
        #        server-addr: nacos.gulimall.svc.cluster.local:8848
      config:
        server-addr: ${nacos_config}
        timeout: 30000
        #        server-addr: nacos.gulimall.svc.cluster.local:8848

其他配置

//k8s
1.15
//spring boot
<parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.2.2.RELEASE</version>
        <relativePath/>
</parent>
//spring cloud alibaba
<parent>
    <groupId>com.alibaba.cloud</groupId>
    <artifactId>spring-cloud-alibaba-starters</artifactId>
    <version>2.2.4.RELEASE</version>
</parent>
//nacos
<dependency>
      <groupId>com.alibaba.nacos</groupId>
      <artifactId>nacos-client</artifactId>
      <version>1.4.1</version>
      <scope>compile</scope>
</dependency>

问题排查

1. 先查了nacos日志，没有任何日志。
2. coredns 当时的日志

2021-06-04T23:23:39.938Z [ERROR] plugin/errors: 2 maya-apiserver-576587998d-7vpsj. AAAA: read udp 10.244.1.191:56724->192.168.8.1:53: i/o timeout
2021-06-04T23:25:39.971Z [ERROR] plugin/errors: 2 maya-apiserver-576587998d-7vpsj. AAAA: read udp 10.244.1.191:57593->192.168.8.1:53: i/o timeout

3. 然后dig cluster 发现正常，如下

root@hp:/# dig -t A nacos.gulimall.svc.cluster.local. @10.244.0.176
; <<>> DiG 9.11.3-1ubuntu1.15-Ubuntu <<>> -t A nacos.gulimall.svc.cluster.local. @10.244.0.176
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49827
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 8a69c8768d24fd61 (echoed)
;; QUESTION SECTION:
;nacos.gulimall.svc.cluster.local. IN	A

;; ANSWER SECTION:
nacos.gulimall.svc.cluster.local. 24 IN	A	10.97.100.187

;; Query time: 0 msec
;; SERVER: 10.244.0.176#53(10.244.0.176)
;; WHEN: Sat Jun 05 12:42:51 CST 2021
;; MSG SIZE  rcvd: 121

使用示例2.0.6就可以，这个问题困扰了大半天，很纠结，因为我是看官方文档来的，原文：
注意：版本 0.2.x.RELEASE 对应的是 Spring Boot 2.x 版本，版本 0.1.x.RELEASE 对应的是 Spring Boot 1.x 版本。

按照文档, 我将一个dubbo项目的 address 从 zookeeper的 127.0.0.1:2181 改为 nacos 的 127.0.0.1:8848, 然后启动时提示 Failed to register dubbo://192.168.50.18:19095/cn.xavier.project.test.api.service.MerchantsRegisterService?anyhost=true&application=project-test-service&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&interface=cn.xavier.project.test.api.service.MerchantsRegisterService&loadbalance=roundrobin&metadata-type=remote&methods=findByNumberCode,updateBankCardInfo,apply,balanceCashQuery,tradeBalanceCashCallback,tradeBalanceCash,wechatConfigQuery,addMerchantsRegister,notifyUrlCallback,findByPossessor,checkDataIntegrity,wechatConfigScheduled,queryMerchantsRegisterList,editMerchantsRegister,merchantBalanceQuery,signCallBackUrlCallback,reportConfig,report,reportCallback&pid=10780&release=2.7.7&revision=1.0.0&service.filter=dubboExceptionFilter, -exception&side=provider&threadpool=fixed&threads=10&timeout=30000&timestamp=1607323364522&version=1.0.0 to registry 127.0.0.1:8848, cause: failed to req API:/nacos/v1/ns/instance after all servers([127.0.0.1:8848]) tried: failed to req API:127.0.0.1:8848/nacos/v1/ns/instance. code:500 msg: caused: Get data failed, key: com.alibaba.nacos.naming.iplist.public##DEFAULT_GROUP@@providers:cn.xavier.project.test.api.service.MerchantsRegisterService:1.0.0:;
log.txt

namespace和 secret-key不用配置吗？
namespace="dev" secret-key="72b02c19-ef70-49de-9395-c4af139ba833"

springboot2使用nacos做配置中心时，服务启动的时候能接受到数据，但是页面修改后服务接受不到新的参数，不能动态刷新。使用提供的demo用例测试：nacos-spring-boot-config-example，测试。发现同样的问题

注：没有引用springcloud，仅仅是springboot服务

类似这样的配置，如何获取

环境：
Springboot 2.3.2
SpringCloudAlibaba 2.2.5

报错提示:
[2021-05-15 23:37:32,812] [ERROR] [com.alibaba.nacos.client.config.http.ServerHttpAgent.httpPost(ServerHttpAgent.java:166)] - [NACOS ConnectException httpPost] currentServerAddr: http://localhost:8848, err : Connection refused (Connection refused) [2021-05-15 23:37:32,813] [ERROR] [com.alibaba.nacos.client.config.http.ServerHttpAgent.httpPost(ServerHttpAgent.java:166)] - [NACOS ConnectException httpPost] currentServerAddr: http://localhost:8848, err : Connection refused (Connection refused) [2021-05-15 23:37:32,814] [ERROR] [com.alibaba.nacos.client.config.http.ServerHttpAgent.httpPost(ServerHttpAgent.java:166)] - [NACOS ConnectException httpPost] currentServerAddr: http://localhost:8848, err : Connection refused (Connection refused) [2021-05-15 23:37:32,815] [ERROR] [com.alibaba.nacos.client.config.http.ServerHttpAgent.httpPost(ServerHttpAgent.java:166)] - [NACOS ConnectException httpPost] currentServerAddr: http://localhost:8848, err : Connection refused (Connection refused) [2021-05-15 23:37:32,815] [ERROR] [com.alibaba.nacos.client.config.impl.ClientWorker.checkUpdateConfigStr(ClientWorker.java:454)] - [fixed-localhost_8848] [check-update] get changed dataId exception java.net.ConnectException: [NACOS HTTP-POST] The maximum number of tolerable server reconnection errors has been reached

Debug发现 localhost:8848的加载优先级比自己配置的快。。。。

Hi,

I follow the https://nacos.io/en-us/docs/quick-start-spring-cloud.html page to come here and download nacos-spring-boot-config-example. I act as what the page said, but the config does not change. Then I found that no such following line in NacosConfigApplication class:

@NacosPropertySource(dataId = "example", autoRefreshed = true)

Then I add it by myself, but it seems no NacosPropertySource annotation in spring-cloud-starter-alibaba-nacos-config-0.2.0.RELEASE. Oh....

The bean 'propertySourcesPlaceholderConfigurer', defined in null, could not be registered. A bean with that name has already been defined in class path resource [org/springframework/boot/autoconfigure/context/PropertyPlaceholderAutoConfiguration.class] and overriding is disabled.

本地启动Nacos服务，并将example-provider和example-consumer注册服务成功，但是通过postman请求consumer接口时，报404，如下所示：

2019-03-25 11:13:25.271 INFO 1169 --- [nio-8002-exec-1] c.n.l.DynamicServerListLoadBalancer : DynamicServerListLoadBalancer for client tairan-spring-cloud-nacos-provider initialized: DynamicServerListLoadBalancer:{NFLoadBalancer:name=tairan-spring-cloud-nacos-provider,current list of Servers=[10.236.173.80:8001],Load balancer stats=Zone stats: {unknown=[Zone:unknown; Instance count:1; Active connections count: 0; Circuit breaker tripped count: 0; Active connections per server: 0.0;]
},Server stats: [[Server:10.236.173.80:8001; Zone:UNKNOWN; Total Requests:0; Successive connection failure:0; Total blackout seconds:0; Last connection made:Thu Jan 01 08:00:00 CST 1970; First connection made: Thu Jan 01 08:00:00 CST 1970; Active Connections:0; total failure count in last (1000) msecs:0; average resp time:0.0; 90 percentile resp time:0.0; 95 percentile resp time:0.0; min resp time:0.0; max resp time:0.0; stddev resp time:0.0]
]}ServerList:org.springframework.cloud.alibaba.nacos.ribbon.NacosServerList@3e424d06
2019-03-25 11:13:25.308 ERROR 1169 --- [nio-8002-exec-1] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.web.client.HttpClientErrorException$NotFound: 404 null] with root cause

org.springframework.web.client.HttpClientErrorException$NotFound: 404 null

nacos-spring-cloud-discovery-example 例子运行报错， 什么原因造成的？

2019-03-20 19:14:15.018 ERROR 8052 --- [ main] o.s.c.a.n.registry.NacosServiceRegistry : nacos registry, service-provider register failed...NacosRegistration{nacosDiscoveryProperties=NacosDiscoveryProperties{serverAddr='xx.xx.xx.xxx:8848', endpoint='', namespace='', logName='', service='service-provider', weight=1.0, clusterName='DEFAULT', metadata={}, registerEnabled=true, ip='192.168.8.78', networkInterface='', port=18080, secure=false, accessKey=', namingLoadCacheAtStart=false', secretKey=''}},

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance after all servers([xx.xx.xx.xxx:8848]) tried
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:335) ~[nacos-client-0.6.2.jar:na]

配置中心dataId如果存在点号“.”会出现异常

nacos.config.remote-first=true 这个配置不起作用，我的是springboot项目，想设置nacos上的配置优先级读取。然后按照官方文档设置nacos.config.remote-first=true，但是不起作用，帮忙看一下，谢谢啦

:: Dubbo Spring Boot (v2.7.4.1) : https://github.com/apache/dubbo-spring-boot-project
:: Dubbo (v2.7.4.1) : https://github.com/apache/incubator-dubbo
:: Discuss group : [email protected]

2020-04-03 10:14:45.555 INFO 12796 --- [ main] e.OverrideDubboConfigApplicationListener : Dubbo Config was overridden by externalized configuration {dubbo.application.qos-enable=false, dubbo.config.multiple=true}
2020-04-03 10:14:45.783 INFO 12796 --- [pool-1-thread-1] .b.c.e.AwaitingNonWebApplicationListener : [Dubbo] Current Spring Boot Application is await...
2020-04-03 10:14:46.983 INFO 12796 --- [ main] e.OverrideDubboConfigApplicationListener : Dubbo Config was overridden by externalized configuration {dubbo.application.name=consumer-dubbo-server, dubbo.application.qos-enable=false, dubbo.config.multiple=true, dubbo.registry.address=nacos://192.168.159.1:8848, dubbo.scan.base-packages=com.around.consumer.dubbo}

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

2020-04-03 10:14:46.993 INFO 12796 --- [ main] c.around.ConsumerDubboServerApplication : The following profiles are active: dev
2020-04-03 10:14:47.243 INFO 12796 --- [ main] .a.d.c.s.c.a.DubboConfigBindingRegistrar : The dubbo config bean definition [name : org.apache.dubbo.config.ApplicationConfig#0, class : org.apache.dubbo.config.ApplicationConfig] has been registered.
2020-04-03 10:14:47.244 INFO 12796 --- [ main] .a.d.c.s.c.a.DubboConfigBindingRegistrar : The BeanPostProcessor bean definition [org.apache.dubbo.config.spring.beans.factory.annotation.DubboConfigBindingBeanPostProcessor] for dubbo config bean [name : org.apache.dubbo.config.ApplicationConfig#0] has been registered.
2020-04-03 10:14:47.244 INFO 12796 --- [ main] .a.d.c.s.c.a.DubboConfigBindingRegistrar : The dubbo config bean definition [name : org.apache.dubbo.config.RegistryConfig#0, class : org.apache.dubbo.config.RegistryConfig] has been registered.
2020-04-03 10:14:47.244 INFO 12796 --- [ main] .a.d.c.s.c.a.DubboConfigBindingRegistrar : The BeanPostProcessor bean definition [org.apache.dubbo.config.spring.beans.factory.annotation.DubboConfigBindingBeanPostProcessor] for dubbo config bean [name : org.apache.dubbo.config.RegistryConfig#0] has been registered.
2020-04-03 10:14:47.307 INFO 12796 --- [ main] b.f.a.ServiceAnnotationBeanPostProcessor : [DUBBO] BeanNameGenerator bean can't be found in BeanFactory with name [org.springframework.context.annotation.internalConfigurationBeanNameGenerator], dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:47.307 INFO 12796 --- [ main] b.f.a.ServiceAnnotationBeanPostProcessor : [DUBBO] BeanNameGenerator will be a instance of org.springframework.context.annotation.AnnotationBeanNameGenerator , it maybe a potential problem on bean name generation., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:47.317 WARN 12796 --- [ main] b.f.a.ServiceAnnotationBeanPostProcessor : [DUBBO] No Spring Bean annotating Dubbo's @service was found under package[com.around.consumer.dubbo], dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:47.318 INFO 12796 --- [ main] o.s.c.a.ConfigurationClassPostProcessor : Cannot enhance @configuration bean definition 'org.apache.dubbo.spring.boot.autoconfigure.DubboRelaxedBinding2AutoConfiguration' since its singleton instance has been created too early. The typical cause is a non-static @bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as 'static'.
2020-04-03 10:14:47.318 INFO 12796 --- [ main] o.s.c.a.ConfigurationClassPostProcessor : Cannot enhance @configuration bean definition 'org.apache.dubbo.spring.boot.autoconfigure.DubboAutoConfiguration' since its singleton instance has been created too early. The typical cause is a non-static @bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as 'static'.
2020-04-03 10:14:47.368 INFO 12796 --- [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=3a1e1f20-e9da-3566-88c7-c4145f05105f
2020-04-03 10:14:47.449 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.autoconfigure.DubboOpenFeignAutoConfiguration' of type [com.alibaba.cloud.dubbo.autoconfigure.DubboOpenFeignAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.499 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'dubbo.cloud-com.alibaba.cloud.dubbo.env.DubboCloudProperties' of type [com.alibaba.cloud.dubbo.env.DubboCloudProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.507 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'metadataJsonResolver' of type [com.alibaba.cloud.dubbo.metadata.resolver.DubboServiceBeanMetadataResolver] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.516 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.apache.dubbo.config.ApplicationConfig#0' of type [org.apache.dubbo.config.ApplicationConfig] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.520 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'dubboProtocolConfigSupplier' of type [com.alibaba.cloud.dubbo.metadata.DubboProtocolConfigSupplier] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.521 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.service.DubboMetadataServiceExporter' of type [com.alibaba.cloud.dubbo.service.DubboMetadataServiceExporter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.521 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.autoconfigure.DubboMetadataAutoConfiguration' of type [com.alibaba.cloud.dubbo.autoconfigure.DubboMetadataAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.523 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.autoconfigure.DubboServiceAutoConfiguration' of type [com.alibaba.cloud.dubbo.autoconfigure.DubboServiceAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.525 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'dubboGenericServiceFactory' of type [com.alibaba.cloud.dubbo.service.DubboGenericServiceFactory] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.528 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'dubboMetadataConfigServiceProxy' of type [com.alibaba.cloud.dubbo.service.DubboMetadataServiceProxy] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.530 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.client.discovery.composite.CompositeDiscoveryClientAutoConfiguration' of type [org.springframework.cloud.client.discovery.composite.CompositeDiscoveryClientAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.532 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.nacos.discovery.NacosDiscoveryClientConfiguration' of type [com.alibaba.cloud.nacos.discovery.NacosDiscoveryClientConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.533 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.nacos.discovery.NacosDiscoveryAutoConfiguration' of type [com.alibaba.cloud.nacos.discovery.NacosDiscoveryAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.539 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.commons.util.UtilAutoConfiguration' of type [org.springframework.cloud.commons.util.UtilAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.542 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'inetUtilsProperties' of type [org.springframework.cloud.commons.util.InetUtilsProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:47.545 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'inetUtils' of type [org.springframework.cloud.commons.util.InetUtils] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:48.696 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'nacosProperties' of type [com.alibaba.cloud.nacos.NacosDiscoveryProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:48.699 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'nacosServiceDiscovery' of type [com.alibaba.cloud.nacos.discovery.NacosServiceDiscovery] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:48.703 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'nacosDiscoveryClient' of type [com.alibaba.cloud.nacos.discovery.NacosDiscoveryClient] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:48.708 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.client.discovery.simple.SimpleDiscoveryClientAutoConfiguration' of type [org.springframework.cloud.client.discovery.simple.SimpleDiscoveryClientAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:49.860 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'simpleDiscoveryProperties' of type [org.springframework.cloud.client.discovery.simple.SimpleDiscoveryProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:49.864 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'simpleDiscoveryClient' of type [org.springframework.cloud.client.discovery.simple.SimpleDiscoveryClient] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:49.866 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'compositeDiscoveryClient' of type [org.springframework.cloud.client.discovery.composite.CompositeDiscoveryClient] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:49.869 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'metadataServiceInstanceSelector' of type [com.alibaba.cloud.dubbo.autoconfigure.DubboMetadataAutoConfiguration$$Lambda$261/2082353865] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:49.873 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.util.JSONUtils' of type [com.alibaba.cloud.dubbo.util.JSONUtils] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.005 WARN 12796 --- [ main] a.c.d.m.r.DubboServiceMetadataRepository : Current application will subscribe all services(size:3) in registry, a lot of memory and CPU cycles may be used, thus it's strongly recommend you using the externalized property 'dubbo.cloud.subscribed-services' to specify the services
2020-04-03 10:14:50.005 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository' of type [com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.013 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.service.parameter.RequestParamServiceParameterResolver' of type [com.alibaba.cloud.dubbo.service.parameter.RequestParamServiceParameterResolver] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.018 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.http.HttpMessageConvertersAutoConfiguration' of type [org.springframework.boot.autoconfigure.http.HttpMessageConvertersAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.021 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.http.HttpMessageConvertersAutoConfiguration$StringHttpMessageConverterConfiguration' of type [org.springframework.boot.autoconfigure.http.HttpMessageConvertersAutoConfiguration$StringHttpMessageConverterConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.023 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.http-org.springframework.boot.autoconfigure.http.HttpProperties' of type [org.springframework.boot.autoconfigure.http.HttpProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.029 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'stringHttpMessageConverter' of type [org.springframework.http.converter.StringHttpMessageConverter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.031 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.http.JacksonHttpMessageConvertersConfiguration$MappingJackson2HttpMessageConverterConfiguration' of type [org.springframework.boot.autoconfigure.http.JacksonHttpMessageConvertersConfiguration$MappingJackson2HttpMessageConverterConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.032 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonObjectMapperConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonObjectMapperConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.034 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonObjectMapperBuilderConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonObjectMapperBuilderConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.035 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$Jackson2ObjectMapperBuilderCustomizerConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$Jackson2ObjectMapperBuilderCustomizerConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.039 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.jackson-org.springframework.boot.autoconfigure.jackson.JacksonProperties' of type [org.springframework.boot.autoconfigure.jackson.JacksonProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.041 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'standardJacksonObjectMapperBuilderCustomizer' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$Jackson2ObjectMapperBuilderCustomizerConfiguration$StandardJackson2ObjectMapperBuilderCustomizer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.044 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.068 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'jsonComponentModule' of type [org.springframework.boot.jackson.JsonComponentModule] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.072 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'jacksonObjectMapperBuilder' of type [org.springframework.http.converter.json.Jackson2ObjectMapperBuilder] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.094 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'jacksonObjectMapper' of type [com.fasterxml.jackson.databind.ObjectMapper] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.101 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'mappingJackson2HttpMessageConverter' of type [org.springframework.http.converter.json.MappingJackson2HttpMessageConverter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.112 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'messageConverters' of type [org.springframework.boot.autoconfigure.http.HttpMessageConverters] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.115 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.service.parameter.RequestBodyServiceParameterResolver' of type [com.alibaba.cloud.dubbo.service.parameter.RequestBodyServiceParameterResolver] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.121 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.service.parameter.RequestHeaderServiceParameterResolver' of type [com.alibaba.cloud.dubbo.service.parameter.RequestHeaderServiceParameterResolver] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.125 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.service.parameter.PathVariableServiceParameterResolver' of type [com.alibaba.cloud.dubbo.service.parameter.PathVariableServiceParameterResolver] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.126 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.dubbo.service.DubboGenericServiceExecutionContextFactory' of type [com.alibaba.cloud.dubbo.service.DubboGenericServiceExecutionContextFactory] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.137 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'relaxedDubboConfigBinder' of type [org.apache.dubbo.spring.boot.autoconfigure.BinderDubboConfigBinder] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.140 INFO 12796 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'relaxedDubboConfigBinder' of type [org.apache.dubbo.spring.boot.autoconfigure.BinderDubboConfigBinder] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-03 10:14:50.194 WARN 12796 --- [ main] c.n.c.sources.URLConfigurationSource : No URLs will be polled as dynamic configuration sources.
2020-04-03 10:14:50.194 INFO 12796 --- [ 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.
2020-04-03 10:14:50.197 WARN 12796 --- [ main] c.n.c.sources.URLConfigurationSource : No URLs will be polled as dynamic configuration sources.
2020-04-03 10:14:50.197 INFO 12796 --- [ 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.
2020-04-03 10:14:50.367 INFO 12796 --- [ main] o.s.s.c.ThreadPoolTaskScheduler : Initializing ExecutorService 'taskScheduler'
2020-04-03 10:14:50.377 INFO 12796 --- [ main] .f.a.DubboConfigBindingBeanPostProcessor : The properties of bean [name : org.apache.dubbo.config.RegistryConfig#0] have been binding by prefix of configuration properties : dubbo.registry
2020-04-03 10:14:50.483 INFO 12796 --- [ main] a.c.d.m.r.DubboServiceMetadataRepository : The metadata of Dubbo service[name : providers:com.alibaba.cloud.dubbo.service.DubboMetadataService:1.0.0:producer-dubbo-server-dev] is about to be initialized
2020-04-03 10:14:50.514 WARN 12796 --- [ main] a.c.d.m.r.DubboServiceMetadataRepository : The Spring application[name : providers:com.alibaba.cloud.dubbo.service.DubboMetadataService:1.0.0:producer-dubbo-server-dev] does not expose The REST metadata in the Dubbo services.
2020-04-03 10:14:50.514 INFO 12796 --- [ main] a.c.d.m.r.DubboServiceMetadataRepository : The metadata of Dubbo service[name : producer-dubbo-server-dev] is about to be initialized
2020-04-03 10:14:50.649 WARN 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] There's no valid metadata config found, if you are using the simplified mode of registry url, please make sure you have a metadata address configured properly., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.652 INFO 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] There's no valid monitor config found, if you want to open monitor statistics for Dubbo, please make sure your monitor is configured properly., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.653 INFO 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] There's no valid monitor config found, if you want to open monitor statistics for Dubbo, please make sure your monitor is configured properly., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.665 INFO 12796 --- [ main] o.a.d.qos.protocol.QosProtocolWrapper : [DUBBO] qos won't be started because it is disabled. Please check dubbo.application.qos.enable is configured either in system property, dubbo.properties or XML/spring-boot configuration., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.665 WARN 12796 --- [ main] o.a.d.c.s.e.SpringExtensionFactory : [DUBBO] No spring extension (bean) named:applicationContext, try to find an extension (bean) of type org.springframework.context.ConfigurableApplicationContext, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.665 WARN 12796 --- [ main] o.a.d.c.s.e.SpringExtensionFactory : [DUBBO] No spring extension (bean) named:applicationContext, type:org.springframework.context.ConfigurableApplicationContext found, stop get bean., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.679 INFO 12796 --- [ main] c.a.c.d.registry.SpringCloudRegistry : [DUBBO] Register: consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=consumers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.683 INFO 12796 --- [ main] c.a.c.d.registry.SpringCloudRegistry : [DUBBO] Subscribe: consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=providers,configurators,routers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.688 INFO 12796 --- [ main] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Load registry cache file C:\Users\moodincode.dubbo\dubbo-registry-consumer-dubbo-server-192.168.159.1:8848.cache, data: {producer-dubbo-server/com.alibaba.cloud.dubbo.service.DubboMetadataService:1.0.0=empty://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=providers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=9184&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585879999594&version=1.0.0}, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.689 INFO 12796 --- [ main] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Register: consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=consumers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.697 INFO 12796 --- [ main] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Subscribe: consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=providers,configurators,routers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.701 INFO 12796 --- [ main] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Notify urls for subscribe url consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=providers,configurators,routers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, urls: [empty://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=providers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0], dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.704 INFO 12796 --- [client.listener] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Notify urls for subscribe url consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=providers,configurators,routers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, urls: [empty://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=providers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0], dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.704 INFO 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] Refer dubbo service org.apache.dubbo.rpc.service.GenericService from url registry://192.168.159.1:8848/org.apache.dubbo.registry.RegistryService?application=consumer-dubbo-server&check=false&cluster=registryaware&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&refer=application%3Dconsumer-dubbo-server%26check%3Dfalse%26dubbo%3D2.0.2%26generic%3Dtrue%26group%3Dproducer-dubbo-server%26interface%3Dcom.alibaba.cloud.dubbo.service.DubboMetadataService%26lazy%3Dfalse%26pid%3D12796%26qos.enable%3Dfalse%26register.ip%3D192.168.159.1%26release%3D2.7.4.1%26side%3Dconsumer%26sticky%3Dfalse%26timestamp%3D1585880090649%26version%3D1.0.0&register.ip=192.168.159.1&registry=nacos&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.714 WARN 12796 --- [ main] a.c.d.m.r.DubboServiceMetadataRepository : The Spring application[name : producer-dubbo-server-dev] does not expose The REST metadata in the Dubbo services.
2020-04-03 10:14:50.714 INFO 12796 --- [ main] a.c.d.m.r.DubboServiceMetadataRepository : The metadata of Dubbo service[name : providers:com.around.producer.dubbo.service.TestDubboServer:1.0.0:] is about to be initialized
2020-04-03 10:14:50.718 WARN 12796 --- [ main] a.c.d.m.r.DubboServiceMetadataRepository : The Spring application[name : providers:com.around.producer.dubbo.service.TestDubboServer:1.0.0:] does not expose The REST metadata in the Dubbo services.
2020-04-03 10:14:50.718 INFO 12796 --- [ main] a.c.d.m.r.DubboServiceMetadataRepository : The metadata of Dubbo services has been initialized
2020-04-03 10:14:50.767 WARN 12796 --- [ scheduling-1] a.c.d.m.r.DubboServiceMetadataRepository : Current application will subscribe all services(size:4) in registry, a lot of memory and CPU cycles may be used, thus it's strongly recommend you using the externalized property 'dubbo.cloud.subscribed-services' to specify the services
2020-04-03 10:14:50.770 INFO 12796 --- [client.listener] a.DubboServiceDiscoveryAutoConfiguration : The event of the service instances[name : providers:com.alibaba.cloud.dubbo.service.DubboMetadataService:1.0.0:producer-dubbo-server-dev , size : 1] change is about to be dispatched
2020-04-03 10:14:50.774 INFO 12796 --- [ main] c.around.ConsumerDubboServerApplication : Started ConsumerDubboServerApplication in 6.797 seconds (JVM running for 8.835)
2020-04-03 10:14:50.776 INFO 12796 --- [client.listener] a.DubboServiceDiscoveryAutoConfiguration : The event of the service instances[name : consumers:com.alibaba.cloud.dubbo.service.DubboMetadataService:1.0.0:producer-dubbo-server , size : 1] change is about to be dispatched
2020-04-03 10:14:50.776 INFO 12796 --- [client.listener] a.DubboServiceDiscoveryAutoConfiguration : The event of the service instances[name : producer-dubbo-server-dev , size : 1] change is about to be dispatched
2020-04-03 10:14:50.776 INFO 12796 --- [client.listener] a.DubboServiceDiscoveryAutoConfiguration : The event of the service instances[name : providers:com.around.producer.dubbo.service.TestDubboServer:1.0.0: , size : 1] change is about to be dispatched
2020-04-03 10:14:50.795 WARN 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] There's no valid metadata config found, if you are using the simplified mode of registry url, please make sure you have a metadata address configured properly., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.806 INFO 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] No valid ip found from environment, try to find valid host from DNS., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.808 WARN 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] Use random available port(20881) for protocol dubbo, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.832 INFO 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] Export dubbo service com.alibaba.cloud.dubbo.service.DubboMetadataService to local registry url : injvm://127.0.0.1/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.832 INFO 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] There's no valid monitor config found, if you want to open monitor statistics for Dubbo, please make sure your monitor is configured properly., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:50.833 INFO 12796 --- [ main] org.apache.dubbo.config.AbstractConfig : [DUBBO] Register dubbo service com.alibaba.cloud.dubbo.service.DubboMetadataService url dubbo://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0 to registry registry://192.168.159.1:8848/org.apache.dubbo.registry.RegistryService?application=consumer-dubbo-server&dubbo=2.0.2&pid=12796&qos.enable=false&registry=nacos&release=2.7.4.1&timestamp=1585880090795, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.601 INFO 12796 --- [ main] o.a.d.remoting.transport.AbstractServer : [DUBBO] Start NettyServer bind /0.0.0.0:20881, export /192.168.159.1:20881, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.603 INFO 12796 --- [ main] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Register: dubbo://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.607 INFO 12796 --- [ main] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Subscribe: provider://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&category=configurators&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.611 INFO 12796 --- [ main] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Notify urls for subscribe url provider://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&category=configurators&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0, urls: [empty://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&category=providers&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0], dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.612 INFO 12796 --- [client.listener] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Notify urls for subscribe url provider://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&category=configurators&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0, urls: [empty://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&category=providers&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0], dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.612 INFO 12796 --- [ main] c.a.c.d.s.DubboMetadataServiceExporter : The Dubbo service[<dubbo:service path="com.alibaba.cloud.dubbo.service.DubboMetadataService" ref="com.alibaba.cloud.dubbo.service.IntrospectiveDubboMetadataService@1115433e" prefix="dubbo.service.com.alibaba.cloud.dubbo.service.DubboMetadataService" generic="false" exported="true" unexported="false" interface="com.alibaba.cloud.dubbo.service.DubboMetadataService" version="1.0.0" dynamic="true" deprecated="false" group="consumer-dubbo-server-dev" id="com.alibaba.cloud.dubbo.service.DubboMetadataService" valid="true" />] has been exported.
2020-04-03 10:14:52.637 ERROR 12796 --- [ main] c.a.c.n.registry.NacosServiceRegistry : nacos registry, consumer-dubbo-server-dev register failed...NacosRegistration{nacosDiscoveryProperties=NacosDiscoveryProperties{serverAddr='192.168.159.1:8848', endpoint='', namespace='', watchDelay=30000, logName='', service='consumer-dubbo-server-dev', weight=1.0, clusterName='DEFAULT', group='DEFAULT_GROUP', namingLoadCacheAtStart='false', metadata={dubbo.metadata-service.urls=[ "dubbo://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0" ], preserved.register.source=SPRING_CLOUD}, registerEnabled=true, ip='10.8.91.228', networkInterface='', port=-1, secure=false, accessKey='', secretKey='', heartBeatInterval=null, heartBeatTimeout=null, ipDeleteTimeout=null}},

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance after all servers([192.168.159.1:8848]) tried: failed to req API:192.168.159.1:8848/nacos/v1/ns/instance. code:500 msg: ErrCode:400, ErrMsg:instance format invalid: Your IP address is spelled incorrectly
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:467) ~[nacos-client-1.1.4.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:389) ~[nacos-client-1.1.4.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.registerService(NamingProxy.java:191) ~[nacos-client-1.1.4.jar:na]
at com.alibaba.nacos.client.naming.NacosNamingService.registerInstance(NacosNamingService.java:207) ~[nacos-client-1.1.4.jar:na]
at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.register(NacosServiceRegistry.java:64) ~[spring-cloud-alibaba-nacos-discovery-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at com.alibaba.cloud.nacos.registry.NacosServiceRegistry$$FastClassBySpringCGLIB$$ca3a8dbd.invoke() [spring-cloud-alibaba-nacos-discovery-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) [spring-core-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:769) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:56) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.aspectj.AspectJAfterAdvice.invoke(AspectJAfterAdvice.java:47) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:689) [spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at com.alibaba.cloud.nacos.registry.NacosServiceRegistry$$EnhancerBySpringCGLIB$$6a7b71cc.register() [spring-cloud-alibaba-nacos-discovery-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at com.alibaba.cloud.dubbo.autoconfigure.DubboServiceRegistrationNonWebApplicationAutoConfiguration.register(DubboServiceRegistrationNonWebApplicationAutoConfiguration.java:92) [spring-cloud-alibaba-dubbo-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at com.alibaba.cloud.dubbo.autoconfigure.DubboServiceRegistrationNonWebApplicationAutoConfiguration.onApplicationStarted(DubboServiceRegistrationNonWebApplicationAutoConfiguration.java:85) [spring-cloud-alibaba-dubbo-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_45]
at org.springframework.context.event.ApplicationListenerMethodAdapter.doInvoke(ApplicationListenerMethodAdapter.java:305) [spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.ApplicationListenerMethodAdapter.processEvent(ApplicationListenerMethodAdapter.java:190) [spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.ApplicationListenerMethodAdapter.onApplicationEvent(ApplicationListenerMethodAdapter.java:153) [spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) [spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) [spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) [spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:403) [spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:360) [spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.boot.context.event.EventPublishingRunListener.started(EventPublishingRunListener.java:98) [spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at org.springframework.boot.SpringApplicationRunListeners.started(SpringApplicationRunListeners.java:71) [spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:321) [spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at com.around.ConsumerDubboServerApplication.main(ConsumerDubboServerApplication.java:14) [classes/:na]

2020-04-03 10:14:52.638 INFO 12796 --- [ main] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Unregister: dubbo://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.643 INFO 12796 --- [ main] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Unsubscribe: provider://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&category=configurators&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.645 INFO 12796 --- [ main] c.a.c.d.s.DubboMetadataServiceExporter : The Dubbo service[<dubbo:service path="com.alibaba.cloud.dubbo.service.DubboMetadataService" ref="com.alibaba.cloud.dubbo.service.IntrospectiveDubboMetadataService@1115433e" prefix="dubbo.service.com.alibaba.cloud.dubbo.service.DubboMetadataService" generic="false" exported="true" unexported="true" interface="com.alibaba.cloud.dubbo.service.DubboMetadataService" version="1.0.0" dynamic="true" deprecated="false" group="consumer-dubbo-server-dev" id="com.alibaba.cloud.dubbo.service.DubboMetadataService" valid="true" />] has been unexported.
2020-04-03 10:14:52.645 INFO 12796 --- [export-thread-1] o.a.d.r.integration.RegistryProtocol : [DUBBO] Waiting 10000ms for registry to notify all consumers before unexport. Usually, this is called when you use dubbo API, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.645 INFO 12796 --- [ main] ConditionEvaluationReportLoggingListener :

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2020-04-03 10:14:52.645 INFO 12796 --- [ main] .b.c.e.AwaitingNonWebApplicationListener : [Dubbo] Current Spring Boot Application is about to shutdown...
2020-04-03 10:14:52.647 INFO 12796 --- [ main] o.s.s.c.ThreadPoolTaskScheduler : Shutting down ExecutorService 'taskScheduler'
2020-04-03 10:14:52.649 INFO 12796 --- [ main] c.a.c.d.s.DubboGenericServiceFactory : The Dubbo GenericService ReferenceBeans are destroying...
2020-04-03 10:14:52.649 INFO 12796 --- [ main] c.a.c.d.s.DubboGenericServiceFactory : Destroyed the ReferenceBean : <dubbo:reference singleton="true" prefix="dubbo.reference.com.alibaba.cloud.dubbo.service.DubboMetadataService" interface="com.alibaba.cloud.dubbo.service.DubboMetadataService" generic="true" version="1.0.0" generic="true" group="producer-dubbo-server" check="false" sticky="false" lazy="false" id="com.alibaba.cloud.dubbo.service.DubboMetadataService" valid="true" />
2020-04-03 10:14:52.650 INFO 12796 --- [ main] f.a.ReferenceAnnotationBeanPostProcessor : class org.apache.dubbo.config.spring.beans.factory.annotation.ReferenceAnnotationBeanPostProcessor was destroying!
2020-04-03 10:14:52.657 ERROR 12796 --- [ main] o.s.boot.SpringApplication : Application run failed

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance after all servers([192.168.159.1:8848]) tried: failed to req API:192.168.159.1:8848/nacos/v1/ns/instance. code:500 msg: ErrCode:400, ErrMsg:instance format invalid: Your IP address is spelled incorrectly
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:467) ~[nacos-client-1.1.4.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:389) ~[nacos-client-1.1.4.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.registerService(NamingProxy.java:191) ~[nacos-client-1.1.4.jar:na]
at com.alibaba.nacos.client.naming.NacosNamingService.registerInstance(NacosNamingService.java:207) ~[nacos-client-1.1.4.jar:na]
at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.register(NacosServiceRegistry.java:64) ~[spring-cloud-alibaba-nacos-discovery-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at com.alibaba.cloud.nacos.registry.NacosServiceRegistry$$FastClassBySpringCGLIB$$ca3a8dbd.invoke() ~[spring-cloud-alibaba-nacos-discovery-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[spring-core-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:769) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:56) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.aspectj.AspectJAfterAdvice.invoke(AspectJAfterAdvice.java:47) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:689) ~[spring-aop-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at com.alibaba.cloud.nacos.registry.NacosServiceRegistry$$EnhancerBySpringCGLIB$$6a7b71cc.register() ~[spring-cloud-alibaba-nacos-discovery-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at com.alibaba.cloud.dubbo.autoconfigure.DubboServiceRegistrationNonWebApplicationAutoConfiguration.register(DubboServiceRegistrationNonWebApplicationAutoConfiguration.java:92) ~[spring-cloud-alibaba-dubbo-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at com.alibaba.cloud.dubbo.autoconfigure.DubboServiceRegistrationNonWebApplicationAutoConfiguration.onApplicationStarted(DubboServiceRegistrationNonWebApplicationAutoConfiguration.java:85) ~[spring-cloud-alibaba-dubbo-2.2.0.RELEASE.jar:2.2.0.RELEASE]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_45]
at org.springframework.context.event.ApplicationListenerMethodAdapter.doInvoke(ApplicationListenerMethodAdapter.java:305) ~[spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.ApplicationListenerMethodAdapter.processEvent(ApplicationListenerMethodAdapter.java:190) ~[spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.ApplicationListenerMethodAdapter.onApplicationEvent(ApplicationListenerMethodAdapter.java:153) ~[spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:403) ~[spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:360) ~[spring-context-5.2.4.RELEASE.jar:5.2.4.RELEASE]
at org.springframework.boot.context.event.EventPublishingRunListener.started(EventPublishingRunListener.java:98) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at org.springframework.boot.SpringApplicationRunListeners.started(SpringApplicationRunListeners.java:71) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:321) [spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
at com.around.ConsumerDubboServerApplication.main(ConsumerDubboServerApplication.java:14) [classes/:na]

2020-04-03 10:14:52.659 INFO 12796 --- [bboShutdownHook] o.apache.dubbo.config.DubboShutdownHook : [DUBBO] Run shutdown hook now., dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.659 INFO 12796 --- [bboShutdownHook] o.a.d.r.support.AbstractRegistryFactory : [DUBBO] Close all registries [nacos://192.168.159.1:8848/org.apache.dubbo.registry.RegistryService?application=consumer-dubbo-server&dubbo=2.0.2&interface=org.apache.dubbo.registry.RegistryService&pid=12796&qos.enable=false&release=2.7.4.1&timestamp=1585880090652], dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.659 INFO 12796 --- [bboShutdownHook] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Destroy registry:nacos://192.168.159.1:8848/org.apache.dubbo.registry.RegistryService?application=consumer-dubbo-server&dubbo=2.0.2&interface=org.apache.dubbo.registry.RegistryService&pid=12796&qos.enable=false&release=2.7.4.1&timestamp=1585880090652, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.659 INFO 12796 --- [bboShutdownHook] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Unregister: consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=consumers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.663 INFO 12796 --- [bboShutdownHook] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Destroy unregister url consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=consumers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.663 INFO 12796 --- [bboShutdownHook] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Unsubscribe: consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=providers,configurators,routers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.663 INFO 12796 --- [bboShutdownHook] o.a.dubbo.registry.nacos.NacosRegistry : [DUBBO] Destroy unsubscribe url consumer://192.168.159.1/org.apache.dubbo.rpc.service.GenericService?application=consumer-dubbo-server&category=providers,configurators,routers&check=false&dubbo=2.0.2&generic=true&group=producer-dubbo-server&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&pid=12796&qos.enable=false&release=2.7.4.1&side=consumer&sticky=false&timestamp=1585880090649&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.663 INFO 12796 --- [bboShutdownHook] o.a.d.rpc.protocol.dubbo.DubboProtocol : [DUBBO] Close dubbo server: /192.168.159.1:20881, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.664 INFO 12796 --- [bboShutdownHook] o.a.d.remoting.transport.AbstractServer : [DUBBO] Close NettyServer bind /0.0.0.0:20881, export /192.168.159.1:20881, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.666 INFO 12796 --- [bboShutdownHook] o.a.d.rpc.protocol.dubbo.DubboProtocol : [DUBBO] Unexport service: dubbo://192.168.159.1:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=consumer-dubbo-server&bind.ip=192.168.159.1&bind.port=20881&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=consumer-dubbo-server-dev&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=12796&qos.enable=false&release=2.7.4.1&revision=2.2.0.RELEASE&side=provider&timestamp=1585880090796&version=1.0.0, dubbo version: 2.7.4.1, current host: 192.168.159.1
2020-04-03 10:14:52.667 INFO 12796 --- [bboShutdownHook] org.apache.dubbo.qos.server.Server : [DUBBO] qos-server stopped., dubbo version: 2.7.4.1, current host: 192.168.159.1
Disconnected from the target VM, address: '127.0.0.1:49199', transport: 'socket'

Process finished with exit code 1

服务无法注册，报这个错误，在window环境下启动的单机模式

2019-07-02 19:32:26.011 ERROR [com.alibaba.nacos.naming.beat.sender:c.a.n.c.naming] request 127.0.0.1:8848 failed.
com.alibaba.nacos.api.exception.NacosException: failed to req API:http://127.0.0.1:8848/nacos/v1/ns/instance/beat. code:400 msg: dom name can only have these characters: 0-9a-zA-Z.:_-; current: DEFAULT_GROUP@@service-consumer

at com.alibaba.nacos.client.naming.net.NamingProxy.callServer(NamingProxy.java:340) [nacos-client-1.0.0.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:367) [nacos-client-1.0.0.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:304) [nacos-client-1.0.0.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.sendBeat(NamingProxy.java:227) [nacos-client-1.0.0.jar:na]
at com.alibaba.nacos.client.naming.beat.BeatReactor$BeatTask.run(BeatReactor.java:109) [nacos-client-1.0.0.jar:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_201]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_201]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_201]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_201]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_201]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_201]

报错日志如下：
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2020-01-09 21:37:08.468 ERROR 16489 --- [ main] o.s.boot.SpringApplication : Application run failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scopedTarget.hostHolder': Scope 'request' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:362) ~[spring-beans-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) ~[spring-beans-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:515) ~[spring-beans-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:503) ~[spring-beans-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.getBeansOfType(AbstractApplicationContext.java:1198) ~[spring-context-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at com.alibaba.nacos.spring.context.event.AnnotationListenerMethodProcessor.processBeans(AnnotationListenerMethodProcessor.java:98) ~[nacos-spring-context-0.2.2-RC1.jar:na]
at com.alibaba.nacos.spring.context.event.AnnotationListenerMethodProcessor.onApplicationEvent(AnnotationListenerMethodProcessor.java:93) ~[nacos-spring-context-0.2.2-RC1.jar:na]
at com.alibaba.nacos.spring.context.event.AnnotationListenerMethodProcessor.onApplicationEvent(AnnotationListenerMethodProcessor.java:52) ~[nacos-spring-context-0.2.2-RC1.jar:na]
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400) ~[spring-context-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:354) ~[spring-context-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:888) ~[spring-context-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:161) ~[spring-boot-2.0.3.RELEASE.jar:2.0.3.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) ~[spring-context-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140) ~[spring-boot-2.0.3.RELEASE.jar:2.0.3.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:759) [spring-boot-2.0.3.RELEASE.jar:2.0.3.RELEASE]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:395) [spring-boot-2.0.3.RELEASE.jar:2.0.3.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:327) [spring-boot-2.0.3.RELEASE.jar:2.0.3.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1255) [spring-boot-2.0.3.RELEASE.jar:2.0.3.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1243) [spring-boot-2.0.3.RELEASE.jar:2.0.3.RELEASE]
at com.alibaba.nacos.example.spring.boot.NacosConfigApplication.main(NacosConfigApplication.java:23) [classes/:na]
Caused by: java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
at org.springframework.web.context.request.RequestContextHolder.currentRequestAttributes(RequestContextHolder.java:131) ~[spring-web-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.web.context.request.AbstractRequestAttributesScope.get(AbstractRequestAttributesScope.java:42) ~[spring-web-5.0.7.RELEASE.jar:5.0.7.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:350) ~[spring-beans-5.0.7.RELEASE.jar:5.0.7.RELEASE]
... 22 common frames omitted

在官方的nacos-spring-boot-config-example下创建以下类
@requestScope(proxyMode = ScopedProxyMode.TARGET_CLASS)
@component
public class HostHolder {

private long userId;

public long getUserId() {
return userId;
}

public void setUserId(long userId) {
this.userId = userId;
}
}
启动项目即可复现该问题

As title says.

如上，使用的代码是nacos-spring-cloud-config-example，修改NacosConfigApplication类：
Environment env = SpringApplication.run(NacosConfigApplication.class, args).getEnvironment(); System.out.println("------ server.port: " + env.getProperty("server.port"));
配置中心中配置demo.properties 配置了server.port，bootstrap.properties正确配置了demo.properties，但是如上print出来的端口是null，通过nacos api可以获取到配置文件 curl -X GET "http://xx:8848/nacos/v1/cs/configs?dataId=sbc-service-setting.properties&group=DEFAULT_GROUP"

@NacosInjected
private NamingService namingService;

@PostConstruct
public void registerInstance() throws NacosException, UnknownHostException {
namingService.registerInstance(applicationName, InetAddress.getLocalHost().getHostAddress(), serverPort,"DEFAULT");
}

通过NamingService 对象来调用注册而不是 Nacos Open API 来注册会失败，请问下是什么 原因

NamingService 也是调用这个接口，参数会生成一些默认填充？？

问题：
在示例的基础上，通过NamingService.registerInstance 方法无法向nacos注册服务，经过单步调试，在NamingProxy.registerService 中
params.put("cluster", JSON.toJSONString(instance.getCluster())); //这一行有问题
this.reqAPI("/nacos/v1/ns/instance", params, (String)"PUT");
在reqAPI方法中http请求的响应提示cluster参数不合法

解决方法
单步调试了一下spring cloud示例，发现spring cloud中引入的nacos-client为0.6.2，而spring boot中引入nacos-client为0.2.1-RC1
调整了一下依赖的版本，排除原来nacos-client 0.2.1-RC1的版本，重新引入0.6.2版本，问题得到解决，
`

        <groupId>com.alibaba.boot</groupId>

        <artifactId>nacos-discovery-spring-boot-starter</artifactId>

        <version>0.2.1</version>

        <exclusions>

            <exclusion>

                <groupId>com.alibaba.nacos</groupId>

                <artifactId>nacos-client</artifactId>

            </exclusion>

        </exclusions>

    </dependency>

    <dependency>

        <groupId>com.alibaba.nacos</groupId>

        <artifactId>nacos-client</artifactId>

        <version>0.6.2</version>

    </dependency>`

请及时调整