1.问题的直接表现（The direct manifestation of the problem）:

org.apache.dubbo.rpc.RpcException: No provider available from registry localhost:9090 for service com.hxy.boot.ticket.articles.api.ArticleService on consumer 192.168.137.1 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist). at org.apache.dubbo.registry.integration.RegistryDirectory.doList(RegistryDirectory.java:599) at org.apache.dubbo.rpc.cluster.directory.AbstractDirectory.list(AbstractDirectory.java:74) at org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.list(AbstractClusterInvoker.java:292) at org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:257) at org.apache.dubbo.rpc.cluster.interceptor.ClusterInterceptor.intercept(ClusterInterceptor.java:47) at org.apache.dubbo.rpc.cluster.support.wrapper.AbstractCluster$InterceptorInvokerNode.invoke(AbstractCluster.java:92) at org.apache.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:88) at org.apache.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:74)

2.问题的直接原因（The direct cause of the problem）:

调用服务提供者时，消费者的dubbo的服务目录 org.apache.dubbo.registry.integration.RegistryDirectory 的 forbidden 属性 为 true，如下图： When the service provider is called, the forbidden property of org.apache.dubbo.registry.integration.RegistryDirectory is true in consumer side. as shown in the following figure:

3.问题的重现（Recurrence of the problem）:

这个问题是偶尔出现的，不容易捕捉。经过分析，在服务提供者的 org.apache.dubbo.config.spring.context.DubboBootstrapApplicationListener#onContextRefreshedEvent(ContextRefreshedEvent event) 的 31行打上断点，并且suspend模式设为 Thread，然后重启服务提供者，就会一直重现此问题。如下图： This problem occurs occasionally and is not easy to catch. After analysis, if a breakpoint is made on line 31 of the service provider's class org.apache.dubbo.config.spring.context.DubboBootstrapApplicationListener#onContextRefreshedEvent(ContextRefreshedEvent event), and the debug suspend mode is set to thread, and then the service provider is restarted, this problem will always recur. as shown in the following figure:

4.问题的根本原因（The root cause of the problem）:

问题的根本原因是spring cloud alibaba框架启动nacos自动服务注册的时点比启动dubbo服务注册的时点早。前者的启动时点是监听到WebServerInitializedEvent事件时(org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration#bind(WebServerInitializedEvent event))，后者的启动时点是监听到ContextRefreshedEvent事件时(org.apache.dubbo.config.spring.context.DubboBootstrapApplicationListener#onContextRefreshedEvent(ContextRefreshedEvent event))。

The root cause of the problem is that the 'spring cloud Alibaba' framework starts Nacos automatic service registration earlier than Dubbo service registration. The starting time of the former is when the 'webserver initialized event' event (org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration#bind(WebServerInitializedEvent event)) is heard, while the latter is when the 'contextrefreshedevent' event (org.apache.dubbo.config.spring.context.DubboBootstrapApplicationListener#onContextRefreshedEvent(ContextRefreshedEvent event)) is monitored.

在spring boot 2.2.x中ServletWebServerInitializedEvent事件的发布是在ContextRefreshedEvent事件之后，如图： In 'spring boot 2.2. X', the 'servlet webserver initialized event' event is published after the 'contextrefreshedevent' event, as shown in the following figure:

但在 spring boot 2.3.x 中改在了ContextRefreshedEvent事件前，如图： However, in 'spring boot 2.3. X', it is changed before the 'contextrefreshedevent' event, as shown in the following figure:

nacos服务端在处理了服务提供者的注册请求后向订阅者下发了实例变更通知，而在这个过程中提供者自身的dubbo服务暴露有可能还没有完成，最直接的表现就是服务提供者的 com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository 的 allExportedURLs属性中还没有对应的dubbo服务的URL。 After processing the registration request of the service provider, the Nacos server sends an instance change notice to the subscriber. In this process, the provider's own Dubbo service exposure may not be completed, and the most direct performance is that: the allexportedurls property of class com.alibaba.cloud.dubbo.metadata.repository.Dubboservicemetadatarepository has no URL for the corresponding Dubbo service.

在第3条的问题重现里面，当程序跑到断点的时候，通过jprofiler查看此时的堆栈信息，可以看到allExportedURLs属性中没有期望的值。 In the problem recurrence in Item 3, when the program runs to a breakpoint, check the stack information through the 'jpprofiler'. You can see that there is no expected value in the 'allexportedurls' attribute.

因为spring cloud alibaba + dubbo 中dubbo的服务是暴露在本地的com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository中的 allExportedURLs 属性中，不会传到注册中心服务端。所以最终暴露完成以后，nacos服务端无法感知到dubbo服务是否已准备妥当，也无法通知订阅者。这种情况下，提供者发起调用时通过泛化调用DubboMetadataService接口获取提供者暴露的服务时，从 allExportedURLs 中获取到的就是一个空的 List<Url>。然后消费者就会以为是没有提供者，于是在自己本地的dubbo服务目录 RegistryDirectory 中 把禁用属性 forbidden 的值更新为了 true。 Because Dubbo's services in spring cloud Alibaba + Dubbo are exposed locally in allexportedurls property of the class com.alibaba.cloud . dubbo.metadata.repository.Dubboservicemetadatarepository. will not be transferred to the registry server.Therefore, after the final exposure is completed, the Nacos server cannot perceive whether the Dubbo service is ready or not, and cannot notify the subscriber.In this case, when a provider initiates a call to obtain the services exposed by the provider through a generalized call to the dubbometadataservice interface, an empty list < URL > is obtained from allexportedurls.Then, the consumer will think that there is no provider, so they update the value of disabled attribute forbidden to true in their local Dubbo service directory registrydirectory.

这时消费者调用提供者时就出现了第1条中的问题。 At this time, the problem in Article 1 arises when the consumer calls the provider.

5.1 应用端解决方案（Application side solutions）:

• 应用启动后，在 ApplicationRunner接口的run方法中，调用 springCloudAlibaba框架中的 NacosServiceRegistry类的setStatus 方法，更新一下在注册中心的实例状态： After the application is started, in the run method of the Applicationrunner interface, call the setstatus method of the Nacosserviceregistry class in the springcloudalibaba framework to update the instance status in the registry server.

` @Component public class NacosServiceInstanceUpAndDownOperator implements ApplicationRunner, Closeable { protected Logger logger = LoggerFactory.getLogger(this.getClass());

/**
 * nacos服务实例上线
 */
private static final String OPERATOR_UP = "UP";
/**
 * nacos服务实例下线
 */
private static final String OPERATOR_DOWN = "DOWN";

@Autowired
NacosServiceRegistry nacosServiceRegistry;

@Autowired
NacosRegistration nacosRegistration;

private ScheduledExecutorService executorService;


@PostConstruct
public void init() {
    int poolSize = 1;
    this.executorService = new ScheduledThreadPoolExecutor(poolSize, new ThreadFactory() {
        @Override
        public Thread newThread(Runnable r) {
            Thread thread = new Thread(r);
            thread.setDaemon(true);
            thread.setName("NacosServiceInstanceUpAndDownOperator");
            return thread;
        }
    });
}


@Override
public void run(ApplicationArguments args) throws Exception {
    long delay_down = 5000L;  //下线任务延迟
    long delay_up = 10000L;   // 上线任务延迟
    this.executorService.schedule(new InstanceDownAndUpTask(nacosServiceRegistry, nacosRegistration, OPERATOR_DOWN), delay_down, TimeUnit.MILLISECONDS);
    this.executorService.schedule(new InstanceDownAndUpTask(nacosServiceRegistry, nacosRegistration, OPERATOR_UP), delay_up, TimeUnit.MILLISECONDS);
}

@Override
public void shutdown() throws NacosException {
    ThreadUtils.shutdownThreadPool(executorService, logger);
}

/**
 * 服务实例上下线任务
 */
class InstanceDownAndUpTask implements Runnable {
    private NacosServiceRegistry nacosServiceRegistry;
    private NacosRegistration nacosRegistration;
    //更新服务实例的状态 ：UP 、DOWN
    private String nacosServiceInstanceOperator;

    InstanceDownAndUpTask(NacosServiceRegistry nacosServiceRegistry, NacosRegistration nacosRegistration, String nacosServiceInstanceOperator) {
        this.nacosServiceRegistry = nacosServiceRegistry;
        this.nacosRegistration = nacosRegistration;
        this.nacosServiceInstanceOperator = nacosServiceInstanceOperator;
    }

    @Override
    public void run() {
        logger.info("===更新nacos服务实例的状态to：{}===start=", nacosServiceInstanceOperator);
        this.nacosServiceRegistry.setStatus(nacosRegistration, nacosServiceInstanceOperator);
        logger.info("===更新nacos服务实例的状态to：{}===end=", nacosServiceInstanceOperator);

        //上线后，关闭线程池
        if (NacosServiceInstanceUpAndDownOperator.OPERATOR_UP.equals(nacosServiceInstanceOperator)) {
            ThreadUtils.shutdownThreadPool(NacosServiceInstanceUpAndDownOperator.this.executorService, NacosServiceInstanceUpAndDownOperator.this.logger);
        }
    }
}

} `

5.2 框架端解决方案的几点意见（Some suggestions on the solution of framework side）:

• a. 调换spring cloud的服务自动注册 和 dubbo服务注册的触发时点（Exchange the trigger time point of automatic service registration of 'spring cloud' and Dubbo service registration）

  让dubbo服务暴露的启动早于spring cloud的服务自动注册。这样的话就需要修改spring cloud commons的源码 和 dubbo 框架的源码，而且动的是根基，感觉不太舒服。

  Make Dubbo service exposed and automatically register services that start earlier than spring cloud.

• b. spring cloud alibaba 中，dubbo服务暴露完成后向nacos注册中心发布一个更新通知（After the Dubbo service exposure is complete, an update notification is issued to the Nacos registry）

• c. spring cloud alibaba 中，添加一个切面，切点为 spring cloud 的服务注册入口，然后在nacos服务注册之前先暴露dubbo服务（Add a aspect to the service registration portal of 'spring cloud'. Then start 'Dubbo' before 'Nacos' service registration to expose Dubbo service:）

  spring cloud alibaba框架中已经有一个现成的切面 DubboServiceRegistrationEventPublishingAspect#beforeRegister(Registration registration) ，可以在前置切点里面再加入dubbo服务的暴露就可以了，但对dubbo框架的服务暴露的过程需要做一些调整，避免在 ContextRefreshedEvent 事件后做一些重复的工作。

[Discuss] the package name & maven groupId & version number

Hi, everyone! now spring-cloud-alibaba have moved away from spring-cloud repository.

The official policy will be announced in the future by spring-cloud team to explain why spring-cloud-alibaba move away from spring-cloud repository.

The package name will be changed from org.springframework.cloud.alibaba to com.alibaba.cloud.

The maven groupId change from org.springframework.cloud to com.alibaba.cloud. maven artifactId will be keep, we think the fewer modification the better.

since the package name & maven groupId modification, the version number will be changed. This is the mapping table between version number modification and Spring Cloud version number.

| Spring Cloud Alibaba Version before change | Spring Cloud Alibaba Version after change | Spring Cloud Version | | :---- | :---- | :----- | | 0.1.x | 1.0.x | Spring Cloud Edgware | | 0.2.x | 1.1.x | Spring Cloud Finchley | | 0.9.x | 1.2.x | Spring Cloud Greenwich |

These modifications will effect the usage of spring-cloud-alibaba, we need the suggestions about package name & maven groupId & version number from community, please reply & discuss in the issue.

[讨论] 关于包名 & maven groupId & 版本号的修改

大家好，spring-cloud-alibaba 目前已经从 spring-cloud 的 github 仓库迁移到了 alibaba 仓库下。

spring-cloud 团队会在未来发出官方的公告解释为什么 spring-cloud-alibaba 会迁移到 alibaba 仓库下。

迁移意味着修改，下面是一些改动点的说明。

包名从 org.springframework.cloud.alibaba 变成 com.alibaba.cloud。

maven groupId 从 org.springframework.cloud 变成 com.alibaba.cloud. maven artifactId 会保持原有的名字，我们认为我们改的越少，大家的改动也就越少。

由于包名和 maven groupId 进行了修改，版本号也需要进行修改，这是版本号修改前后跟 Spring Cloud 版本号的映射关系表：

| Spring Cloud Alibaba 修改前的版本 | Spring Cloud Alibaba 修改后的版本 | Spring Cloud 版本 | | :---- | :---- | :----- | | 0.1.x | 1.0.x | Spring Cloud Edgware | | 0.2.x | 1.1.x | Spring Cloud Finchley | | 0.9.x | 1.2.x | Spring Cloud Greenwich |

这些包名和 maven groupId 以及版本号的修改会影响目前 spring-cloud-alibaba 的使用者，我们需要社区的意见，也想听听社区的声音。大家可以在 issue 里进行答复和讨论。

Spring Cloud Dubbo组件去留问题讨论

由于Spring Cloud Dubbo组件社区做了一些调研发现真正深度使用的用户不多，另外该模块设计本身存在一些问题成熟度不够，复杂度很高，长期缺乏维护答疑同学，因此为了降低社区维护成本，社区第4次双周会讨论觉得将Spring Cloud Dubbo从社区主干分支中移除可能更适合社区当前发展规划。社区未来的工作中心将在维护现有其他组件的稳定性的前提下，提升Spring Cloud Alibaba的微服务治理能力上，对相关建设感兴趣的同学也可以参与到社区的相关功能的建设上来，具体可参见：建设文档。你是否支持社区从主干中移除Spring Cloud Dubbo模块呢？无论是否支持都可以在本issue下进行留言，你的宝贵意见也是Spring Cloud Alibaba社区规划决策的重要信息来源！

Discussion on the problem of leaving and leaving Spring Cloud Dubbo components

We has done some research and found the Spring Cloud Dubbo component there are not many users who really use it deeply, and there are some problems in the design of the module itself, the maturity is not enough, the complexity is high, and there is a long-term lack of maintenance and answering contributors. Therefore, in order to reduce the cost of community maintenance, the community The 4th biweekly meeting discussed that it may be more suitable for the current development plan of the community to remove Spring Cloud Dubbo from the main branch of the community. The future work of the community will improve the microservices governance capabilities of Spring Cloud Alibaba on the premise of maintaining the stability of other existing components.People who are interested in related construction can also participate in the construction of related functions of the community. See: Construction Documentation. Do you support the community to remove the Spring Cloud Dubbo module from repository? Whether you support it or not, you can leave a comment under this issue. Your valuable opinions are also an important source of information for the planning and decision-making of the Spring Cloud Alibaba community!

What do you expect from Spring Cloud Alibaba

The Spring Cloud Alibaba community is making plans for 2022. You are welcome to leave a message to us about your thoughts.

你对Spring Cloud Alibaba有什么期待？

Spring Cloud Alibaba社区正在做2022年度规划，欢迎大家将自己的相关想法留言告诉我们：）

alibaba/nacos#1552 Issue Description

Describe what happened (or what feature you want)

使用nacos 1.1.4 docker mysql 单机版部署，总共遇到两个问题 1、修改配置后，配置不能及时生效，必须手动重启nacos(该问题每次都能复现) 2、当增加dataID 大于11条时，再次增加第12个配置时，新增的dataID 不能在列表上显示

Describe what you expected to happen

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

docker-compose -f example/standalone-mysql.yaml up

Anything else we need to know?

docker compose

nacos:
    image: '10.30.161.199:5000/nacos/nacos-server:1.1.4'
    container_name: nacos-standalone
    environment:
      - MODE=standalone
      - SPRING_DATASOURCE_PLATFORM=mysql
      - MYSQL_MASTER_SERVICE_HOST=mysql
      - MYSQL_MASTER_SERVICE_DB_NAME=nacos-config
      - MYSQL_MASTER_SERVICE_PORT=3306
      - MYSQL_MASTER_SERVICE_USER=root
      - MYSQL_MASTER_SERVICE_PASSWORD=tKWH0FQGZmNjgQRyNq9stDS0IXDtxXmx
      - MYSQL_DATABASE_NUM=1
    ports:
      - "8848:8848"
      - "9555:9555"
    depends_on:
      - mysql
    restart: on-failure
    deploy:
      placement:
        constraints: [node.labels.nacos==true]

Background

Spring Boot 3.0 release General Availability(GA) version yesterday, you can refer to https://spring.io/blog/2022/11/24/spring-boot-3-0-goes-ga

Discussion

About Spring Boot 3.0, What is your demand? You can tell us by leaving message below.

Which Component Eureka 或者Nacos Discovery, Dubbo

Describe the bug

nacos或者eureka作为服务注册中心，服务A订阅了B服务，服务B订阅了C、D服务，当D服务Down机，会导致A调用B，B调用C服务出现“No provider available”，反之C服务Down机也会有这种问题

Nacos or Eureka is the service registry. Service a subscribes to service B, and service B subscribes to services C and D. when service d is down, a calls B, and B calls C, and "no provider available" occurs. Otherwise, service C is down

服务提供方配置B： Service provider configuration B:

dubbo: cloud: subscribed-services: 'C,D' consumer: check: false client: netty retries: 0 threadpool: fixed threads: 200 queues: 0 loadbalance: 'roundrobin' init: true

scan: base-packages: cn.retail.product protocol: name: dubbo port: 20900 client: netty server: netty serialization: hessian2 charset: utf-8 threadpool: fixed threads: 200 queues: 0 iothreads: 9 buffer: 8192 accepts: 1000 payload: 8388608 dispatcher: all

registry: check: false file: './dubbo/dubbo-registry-product-service.cache' address: 'spring-cloud://192.168.30.221' port: 32505

provider: filter: '-exception' loadbalance: 'roundrobin' cluster: 'failover'

服务消费者A： Service consumer A:

dubbo: cloud: subscribed-services: 'B' consumer: check: false client: netty retries: 0 threadpool: fixed threads: 200 queues: 0 loadbalance: 'roundrobin'

eureka: instance: prefer-ip-address: true lease-renewal-interval-in-seconds: 5 lease-expiration-duration-in-seconds: 10 client: enabled: true registry-fetch-interval-seconds: 10 eureka-service-url-poll-interval-seconds: 5 service-url: defaultZone:'http://192.168.30.221:32505/eureka/,http://192.168.30.221:32506/eureka/,http://192.168.30.221:32507/eureka/'

不清楚，是否为springcloud alibaba duboo bug导致

I don't know if it is caused by the springcloud Alibaba dubbo bug

Which Component Nacos Discovery, Dubbo

Describe the bug

nacos作为服务注册中心，当服务端掉线（服务实例改变事件），dubbo重连任务每隔1分钟不间断进行。原因可能是spring-cloud-alibaba没有把服务实例改变消息传递进dubbo，也有可能是dubbo没有处理这个消息

Nacos serves as the service registry. When the service end drops the line (service instance change event), Dubbo reconnection task will continue every 1 minute. The reason may be that spring cloud Alibaba did not deliver the service instance change message to Dubbo, or Dubbo did not process the message

To Reproduce Steps to reproduce the behavior: 配置服务端和消费端的注册中心为nacos： 1.服务端参数：dubbo.protocol.name=dubbo，dubbo.protocol.port=28801，dubbo.scan.base-packages=xx.xx.xx，dubbo.registry.address=spring-cloud://localhost 2.消费端参数：dubbo.consumer.check=false，dubbo.registry.address=spring-cloud://localhost 3. 启动服务端和消费端 4.修改服务端dubbo监听端口为： dubbo.protocol.port=28802 5.重启服务端 6. 消费端服务端业务正常。但消费端持续不断每隔1分钟连接服务端旧的28801端口。

配置服务端和消费端的注册中心为zookeeper： 1.服务端参数：dubbo.protocol.name=dubbo，dubbo.protocol.port=28801，dubbo.scan.base-packages=xx.xx.xx，dubbo.registry.address=zookeeper://127.0.0.1:2181 2.消费端参数：dubbo.consumer.check=false，dubbo.registry.address=zookeeper://127.0.0.1:2181 3. 启动服务端和消费端 4.修改服务端dubbo监听端口为： dubbo.protocol.port=28802 5.重启服务端 6. 消费端不会连接服务端旧的28801端口。消费端服务端业务正常。

以上场景模拟在docker容器中的场景，在docker容器中，微服务经常重新启动，重启微服务以后，其ip地址会发生变化（此处用端口变化模拟地址变化，道理是一样的）。

结论： 1、zookeeper作为服务注册中心，没有问题， 2、nacos作为服务注册中心，当服务端掉线（服务实例改变事件）并未处理该通道，造成重连任务不断进行。原因可能是spring-cloud-alibaba没有把服务实例改变消息传递进dubbo，也有可能是dubbo没有处理这个消息

Configure the registry of the server and the consumer as Nacos:

1. Server parameters: Dubbo. Protocol. Name = Dubbo, Dubbo. Protocol. Port = 28801, Dubbo. Scan. Base packages = xx.xx.xx, Dubbo. Registry. Address = spring cloud: / / localhost
2. Consumer parameters: Dubbo. Consumer. Check = false, Dubbo. Registry. Address = spring cloud: / / localhost
3. Start the service end and the consumer end
4. Modify the Dubbo monitoring port of the server as: Dubbo. Protocol. Port = 28802
5. Restart the server
6. The service end business of the consumer end is normal. However, the consumer continues to connect to the old 28801 port of the server every 1 minute.

Configure the registry of the server and consumer as zookeeper:

1. Server parameters: Dubbo. Protocol. Name = Dubbo, Dubbo. Protocol. Port = 28801, Dubbo. Scan. Base packages = xx.xx.xx, Dubbo. Registry. Address = zookeeper: / / 127.0.0.1:2181
2. Consumer parameters: Dubbo. Consumer. Check = false, Dubbo. Registry. Address = zookeeper: / / 127.0.0.1:2181
3. Start the service end and the consumer end
4. Modify the Dubbo monitoring port of the server as: Dubbo. Protocol. Port = 28802
5. Restart the server
6. The consumer will not connect to the old 28801 port of the server. The service end business of the consumer end is normal.

The above scenario simulates the scenario in the docker container. In the docker container, the microservice is often restarted. After restarting the microservice, its IP address will change (Port change is used here to simulate address change, the same principle).

Conclusion:

1. Zookeeper as the service registry, no problem,
2. As a service registry, Nacos does not handle the channel when the service end drops the line (service instance change event), resulting in the continuous reconnection task. The reason may be that spring cloud Alibaba did not deliver the service instance change message to Dubbo, or Dubbo did not process the message

Expected behavior

Expect Nacos as a registry as normal as zookeeper

Screenshots

Additional context CentOS 7.5 、Java8 、 Version 2.2.0.RELEASE

前几天把项目的spring-cloud-gateway版本升级到了3.1.1，nacos的版本升级到2021.0.1.0，发现启动不了。 debug看了下，是阻塞在了WeightCalculatorWebFilter类locator.getRoutes().blockLast()这个地方。 邮件问了下鬼佬，他说不知道为什么，就不鸟我了。 后来在配置文件里加了下spring.cloud.gateway.predicate.weight.enabled=false，可以启动起来了。 不知道各位大佬，有没有谁知道这是什么原因导致的？

public void onApplicationEvent(ApplicationEvent event) {
	if (event instanceof PredicateArgsEvent) {
		handle((PredicateArgsEvent) event);
	}
	else if (event instanceof WeightDefinedEvent) {
		addWeightConfig(((WeightDefinedEvent) event).getWeightConfig());
	}
	else if (event instanceof RefreshRoutesEvent && routeLocator != null) {
		// forces initialization
		if (routeLocatorInitialized.compareAndSet(false, true)) {
			// on first time, block so that app fails to start if there are errors in
			// routes
			// see gh-1574
			routeLocator.ifAvailable(locator -> locator.getRoutes().blockLast());
		}
		else {
			// this preserves previous behaviour on refresh, this could likely go away
			routeLocator.ifAvailable(locator -> locator.getRoutes().subscribe());
		}
	}

}

问下各位大佬， nacos现在动态发布配置的机制是依赖spring的RefreshScope注解，RefreshScope注解配在配置所在的类头上，类似于这样：

服务在线的情况下，发布这个配置，这会导致spring上下文重新加载，导致服务重启，表现为在注册中心（如eureka）上先down一下然后再up（虽然这个过程可能非常快），，为什么nacos不采用类似apollo的动态发布方式，也就是通过beanFactory找到对应的配置所在的类，然后用反射的方式修改具体配置的值，这样整个spring上下文是不重启的，服务不会重启。

这个说是springcloud/springcloudalibaba的标准导致目前的这个现状，所以在这里问问

Which Component nacos 1.2.1, Spring Cloud Alibaba 2.2.1.RELEASE, Spring Cloud Hoxton.SR3, spring-boot 2.2.6

Describe what problem you have encountered
After my repeated tests, after starting the service provider and then starting the service consumer, the service consumer initiated an interface call to get an exception：（No provider available from registry localhost:9090 for service XXXXX use dubbo version 2.7.6, please check status of providers(disabled, not registered or in blacklist).）otherwise there is no problem, All my services are under the same group.

Which Component Nacos Discovery

Describe the bug I ran mvn native:compile on Ubuntu and successfully got an executable native file. When I started this app, I got some error logs and then the app shutdown. And then I also did this work on Windows and it failed because of the same reason!

To Reproduce Native App Running logs:

2023-01-01T16:02:21.917+08:00  INFO 27086 --- [           main] c.a.n.client.env.SearchableProperties    : properties search order:PROPERTIES->JVM->ENV->DEFAULT_SETTING
2023-01-01T16:02:21.917+08:00  WARN 27086 --- [           main] c.a.nacos.client.logging.NacosLogging    : Load Logback Configuration of Nacos fail, message: org.slf4j.impl.StaticLoggerBinder

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v3.0.0)

2023-01-01T16:02:21.920+08:00  INFO 27086 --- [           main] com.example.demo.Demo4Application        : Starting AOT-processed Demo4Application using Java 17.0.5 with PID 27086 (/home/jmc/demo4/build/native/nativeCompile/demo4 started by root in /home/jmc/demo4/build/native/nativeCompile)
2023-01-01T16:02:21.920+08:00  INFO 27086 --- [           main] com.example.demo.Demo4Application        : No active profile set, falling back to 1 default profile: "default"
2023-01-01T16:02:21.921+08:00  INFO 27086 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=f880f0b5-e998-3381-a879-8fb548c73dff
2023-01-01T16:02:21.931+08:00  INFO 27086 --- [           main] o.s.b.w.embedded.tomcat.TaomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
2023-01-01T16:02:21.932+08:00  INFO 27086 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2023-01-01T16:02:21.932+08:00  INFO 27086 --- [           main] o.apache.catalina.core.StandardEngine    : Starting Servlet engine: [Apache Tomcat/10.1.1]
2023-01-01T16:02:21.936+08:00  INFO 27086 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2023-01-01T16:02:21.936+08:00  INFO 27086 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 16 ms
2023-01-01T16:02:22.962+08:00  INFO 27086 --- [           main] o.s.cloud.commons.util.InetUtils         : Cannot determine local hostname
2023-01-01T16:02:23.966+08:00  INFO 27086 --- [           main] o.s.cloud.commons.util.InetUtils         : Cannot determine local hostname
2023-01-01T16:02:23.985+08:00  INFO 27086 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
2023-01-01T16:02:23.985+08:00  INFO 27086 --- [           main] c.a.n.client.env.SearchableProperties    : properties search order:PROPERTIES->JVM->ENV->DEFAULT_SETTING
2023-01-01T16:02:23.986+08:00  WARN 27086 --- [           main] c.a.nacos.client.logging.NacosLogging    : Load Logback Configuration of Nacos fail, message: org.slf4j.impl.StaticLoggerBinder
2023-01-01T16:02:23.986+08:00  INFO 27086 --- [           main] com.alibaba.nacos.client.naming          : initializer namespace from System Property : null
2023-01-01T16:02:23.986+08:00  INFO 27086 --- [           main] com.alibaba.nacos.client.naming          : initializer namespace from System Environment :null
2023-01-01T16:02:23.986+08:00  INFO 27086 --- [           main] com.alibaba.nacos.client.naming          : initializer namespace from System Property :
2023-01-01T16:02:23.988+08:00 ERROR 27086 --- [           main] c.a.nacos.common.notify.NotifyCenter     : Service class newInstance has error :

java.lang.InstantiationException: com.alibaba.nacos.common.notify.DefaultPublisher
        at [email protected]/java.lang.Class.newInstance(DynamicHub.java:639) ~[demo4:na]
        at com.alibaba.nacos.common.notify.NotifyCenter.lambda$static$0(NotifyCenter.java:89) ~[na:na]
        at com.alibaba.nacos.common.notify.EventPublisherFactory.apply(EventPublisherFactory.java:26) ~[demo4:na]
        at com.alibaba.nacos.common.utils.MapUtil.computeIfAbsent(MapUtil.java:153) ~[na:na]
        at com.alibaba.nacos.common.notify.NotifyCenter.registerToPublisher(NotifyCenter.java:347) ~[na:na]
        at com.alibaba.nacos.common.notify.NotifyCenter.registerToPublisher(NotifyCenter.java:328) ~[na:na]
        at com.alibaba.nacos.client.naming.NacosNamingService.init(NacosNamingService.java:99) ~[na:na]
        at com.alibaba.nacos.client.naming.NacosNamingService.<init>(NacosNamingService.java:85) ~[na:na]
        at [email protected]/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) ~[demo4:na]
        at [email protected]/java.lang.reflect.Constructor.newInstance(Constructor.java:480) ~[demo4:na]
        at com.alibaba.nacos.api.naming.NamingFactory.createNamingService(NamingFactory.java:59) ~[na:na]
        at com.alibaba.nacos.api.NacosFactory.createNamingService(NacosFactory.java:77) ~[na:na]
        at com.alibaba.cloud.nacos.NacosServiceManager.createNewNamingService(NacosServiceManager.java:99) ~[demo4:2022.0.0.0-RC1]
        at com.alibaba.cloud.nacos.NacosServiceManager.buildNamingService(NacosServiceManager.java:90) ~[demo4:2022.0.0.0-RC1]
        at com.alibaba.cloud.nacos.NacosServiceManager.getNamingService(NacosServiceManager.java:46) ~[demo4:2022.0.0.0-RC1]
        at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.namingService(NacosServiceRegistry.java:193) ~[demo4:2022.0.0.0-RC1]
        at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.register(NacosServiceRegistry.java:68) ~[demo4:2022.0.0.0-RC1]
        at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.register(AbstractAutoServiceRegistration.java:264) ~[demo4:4.0.0]
        at com.alibaba.cloud.nacos.registry.NacosAutoServiceRegistration.register(NacosAutoServiceRegistration.java:78) ~[demo4:2022.0.0.0-RC1]
        at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.start(AbstractAutoServiceRegistration.java:156) ~[demo4:4.0.0]
        at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:119) ~[demo4:4.0.0]
        at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:49) ~[demo4:4.0.0]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176) ~[na:na]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169) ~[na:na]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143) ~[na:na]
        at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:413) ~[demo4:6.0.2]
        at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:370) ~[demo4:6.0.2]
        at org.springframework.boot.web.servlet.context.WebServerStartStopLifecycle.start(WebServerStartStopLifecycle.java:47) ~[na:na]
        at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:178) ~[demo4:6.0.2]
        at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:356) ~[na:na]
        at [email protected]/java.lang.Iterable.forEach(Iterable.java:75) ~[demo4:na]
        at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:155) ~[demo4:6.0.2]
        at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:123) ~[demo4:6.0.2]
        at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:932) ~[demo4:6.0.2]
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:587) ~[demo4:6.0.2]
        at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:730) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:432) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:308) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1302) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1291) ~[demo4:3.0.0]
        at com.example.demo.Demo4Application.main(Demo4Application.java:10) ~[demo4:na]
Caused by: java.lang.NoSuchMethodException: com.alibaba.nacos.common.notify.DefaultPublisher.<init>()
        at [email protected]/java.lang.Class.getConstructor0(DynamicHub.java:3585) ~[demo4:na]
        at [email protected]/java.lang.Class.newInstance(DynamicHub.java:626) ~[demo4:na]
        ... 41 common frames omitted

2023-01-01T16:02:23.988+08:00  WARN 27086 --- [           main] w.s.c.ServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Failed to start bean 'webServerStartStop'
2023-01-01T16:02:23.990+08:00  INFO 27086 --- [           main] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]
2023-01-01T16:02:23.992+08:00 ERROR 27086 --- [           main] o.s.boot.SpringApplication               : Application run failed

org.springframework.context.ApplicationContextException: Failed to start bean 'webServerStartStop'
        at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:181) ~[demo4:6.0.2]
        at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:356) ~[na:na]
        at [email protected]/java.lang.Iterable.forEach(Iterable.java:75) ~[demo4:na]
        at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:155) ~[demo4:6.0.2]
        at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:123) ~[demo4:6.0.2]
        at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:932) ~[demo4:6.0.2]
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:587) ~[demo4:6.0.2]
        at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:730) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:432) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:308) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1302) ~[demo4:3.0.0]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1291) ~[demo4:3.0.0]
        at com.example.demo.Demo4Application.main(Demo4Application.java:10) ~[demo4:na]
Caused by: java.lang.RuntimeException: ErrCode:-400, ErrMsg:com.alibaba.nacos.common.notify.DefaultPublisher.<init>()
        at com.alibaba.cloud.nacos.NacosServiceManager.createNewNamingService(NacosServiceManager.java:102) ~[demo4:2022.0.0.0-RC1]
        at com.alibaba.cloud.nacos.NacosServiceManager.buildNamingService(NacosServiceManager.java:90) ~[demo4:2022.0.0.0-RC1]
        at com.alibaba.cloud.nacos.NacosServiceManager.getNamingService(NacosServiceManager.java:46) ~[demo4:2022.0.0.0-RC1]
        at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.namingService(NacosServiceRegistry.java:193) ~[demo4:2022.0.0.0-RC1]
        at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.register(NacosServiceRegistry.java:68) ~[demo4:2022.0.0.0-RC1]
        at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.register(AbstractAutoServiceRegistration.java:264) ~[demo4:4.0.0]
        at com.alibaba.cloud.nacos.registry.NacosAutoServiceRegistration.register(NacosAutoServiceRegistration.java:78) ~[demo4:2022.0.0.0-RC1]
        at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.start(AbstractAutoServiceRegistration.java:156) ~[demo4:4.0.0]
        at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:119) ~[demo4:4.0.0]
        at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:49) ~[demo4:4.0.0]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176) ~[na:na]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169) ~[na:na]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143) ~[na:na]
        at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:413) ~[demo4:6.0.2]
        at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:370) ~[demo4:6.0.2]
        at org.springframework.boot.web.servlet.context.WebServerStartStopLifecycle.start(WebServerStartStopLifecycle.java:47) ~[na:na]
        at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:178) ~[demo4:6.0.2]
        ... 13 common frames omitted
Caused by: com.alibaba.nacos.api.exception.NacosException: java.lang.reflect.InvocationTargetException
        at com.alibaba.nacos.api.naming.NamingFactory.createNamingService(NamingFactory.java:61) ~[na:na]
        at com.alibaba.nacos.api.NacosFactory.createNamingService(NacosFactory.java:77) ~[na:na]
        at com.alibaba.cloud.nacos.NacosServiceManager.createNewNamingService(NacosServiceManager.java:99) ~[demo4:2022.0.0.0-RC1]
        ... 29 common frames omitted
Caused by: java.lang.reflect.InvocationTargetException: null
        at [email protected]/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) ~[demo4:na]
        at [email protected]/java.lang.reflect.Constructor.newInstance(Constructor.java:480) ~[demo4:na]
        at com.alibaba.nacos.api.naming.NamingFactory.createNamingService(NamingFactory.java:59) ~[na:na]
        ... 31 common frames omitted
Caused by: com.alibaba.nacos.api.exception.runtime.NacosRuntimeException: java.lang.InstantiationException: com.alibaba.nacos.common.notify.DefaultPublisher
        at com.alibaba.nacos.common.notify.NotifyCenter.lambda$static$0(NotifyCenter.java:94) ~[na:na]
        at com.alibaba.nacos.common.notify.EventPublisherFactory.apply(EventPublisherFactory.java:26) ~[demo4:na]
        at com.alibaba.nacos.common.utils.MapUtil.computeIfAbsent(MapUtil.java:153) ~[na:na]
        at com.alibaba.nacos.common.notify.NotifyCenter.registerToPublisher(NotifyCenter.java:347) ~[na:na]
        at com.alibaba.nacos.common.notify.NotifyCenter.registerToPublisher(NotifyCenter.java:328) ~[na:na]
        at com.alibaba.nacos.client.naming.NacosNamingService.init(NacosNamingService.java:99) ~[na:na]
        at com.alibaba.nacos.client.naming.NacosNamingService.<init>(NacosNamingService.java:85) ~[na:na]
        ... 34 common frames omitted
Caused by: java.lang.InstantiationException: com.alibaba.nacos.common.notify.DefaultPublisher
        at [email protected]/java.lang.Class.newInstance(DynamicHub.java:639) ~[demo4:na]
        at com.alibaba.nacos.common.notify.NotifyCenter.lambda$static$0(NotifyCenter.java:89) ~[na:na]
        ... 40 common frames omitted
Caused by: java.lang.NoSuchMethodException: com.alibaba.nacos.common.notify.DefaultPublisher.<init>()
        at [email protected]/java.lang.Class.getConstructor0(DynamicHub.java:3585) ~[demo4:na]
        at [email protected]/java.lang.Class.newInstance(DynamicHub.java:626) ~[demo4:na]
        ... 41 common frames omitted

2023-01-01T16:02:24.002+08:00  WARN 27086 --- [       Thread-4] c.a.nacos.common.notify.NotifyCenter     : [NotifyCenter] Start destroying Publisher
2023-01-01T16:02:24.002+08:00  WARN 27086 --- [       Thread-4] c.a.nacos.common.notify.NotifyCenter     : [NotifyCenter] Destruction of the end

Maven pom file:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>com.example</groupId>
    <artifactId>demo4</artifactId>
    <version>1.0.0</version>

    <properties>
        <java.version>17</java.version>
    </properties>

    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>3.0.0</version>
        <relativePath/>
    </parent>

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

        <dependency>
            <groupId>com.alibaba.cloud</groupId>
            <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId>
        </dependency>
    </dependencies>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>com.alibaba.cloud</groupId>
                <artifactId>spring-cloud-alibaba-dependencies</artifactId>
                <version>2022.0.0.0-RC1</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>
        </plugins>
    </build>
</project>

mvn native:compile running logs:

root@Jmc-PC:/home/jmc/demo4# ./mvnw native:compile
[INFO] Scanning for projects...
[INFO]
[INFO] -------------------------< com.example:demo4 >--------------------------
[INFO] Building demo4 1.0.0
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] >>> native-maven-plugin:0.9.18:compile (default-cli) > package @ demo4 >>>
[INFO]
[INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ demo4 ---
[INFO] Copying 1 resource
[INFO] Copying 0 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ demo4 ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.3.0:testResources (default-testResources) @ demo4 ---
[INFO] skip non existing resourceDirectory /home/jmc/demo4/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:testCompile (default-testCompile) @ demo4 ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @ demo4 ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:3.3.0:jar (default-jar) @ demo4 ---
[INFO]
[INFO] --- spring-boot-maven-plugin:3.0.0:repackage (repackage) @ demo4 ---
[INFO] Replacing main artifact with repackaged archive
[INFO]
[INFO] <<< native-maven-plugin:0.9.18:compile (default-cli) < package @ demo4 <<<
[INFO]
[INFO]
[INFO] --- native-maven-plugin:0.9.18:compile (default-cli) @ demo4 ---
[INFO] Found GraalVM installation from JAVA_HOME variable.
[WARNING] Properties file at 'jar:file:///root/.m2/repository/com/alibaba/nacos/nacos-client/2.2.1-RC/nacos-client-2.2.1-RC.jar!/META-INF/native-image/io.netty/common/native-image.properties' does not match the recommended 'META-INF/native-image/com.alibaba.nacos/nacos-client/native-image.properties' layout.
[WARNING] Properties file at 'jar:file:///root/.m2/repository/com/alibaba/nacos/nacos-client/2.2.1-RC/nacos-client-2.2.1-RC.jar!/META-INF/native-image/io.netty/buffer/native-image.properties' does not match the recommended 'META-INF/native-image/com.alibaba.nacos/nacos-client/native-image.properties' layout.
[WARNING] Properties file at 'jar:file:///root/.m2/repository/com/alibaba/nacos/nacos-client/2.2.1-RC/nacos-client-2.2.1-RC.jar!/META-INF/native-image/io.netty/transport/native-image.properties' does not match the recommended 'META-INF/native-image/com.alibaba.nacos/nacos-client/native-image.properties' layout.
[WARNING] Properties file at 'jar:file:///root/.m2/repository/com/alibaba/nacos/nacos-client/2.2.1-RC/nacos-client-2.2.1-RC.jar!/META-INF/native-image/io.netty/handler/native-image.properties' does not match the recommended 'META-INF/native-image/com.alibaba.nacos/nacos-client/native-image.properties' layout.
[WARNING] Properties file at 'jar:file:///root/.m2/repository/com/alibaba/nacos/nacos-client/2.2.1-RC/nacos-client-2.2.1-RC.jar!/META-INF/native-image/io.netty/codec-http/native-image.properties' does not match the recommended 'META-INF/native-image/com.alibaba.nacos/nacos-client/native-image.properties' layout.
[WARNING] Properties file at 'jar:file:///root/.m2/repository/com/alibaba/nacos/nacos-client/2.2.1-RC/nacos-client-2.2.1-RC.jar!/META-INF/native-image/io.netty/codec-http2/native-image.properties' does not match the recommended 'META-INF/native-image/com.alibaba.nacos/nacos-client/native-image.properties' layout.
[INFO] Executing: /root/graalvm-ce-java17-22.3.0/bin/native-image -cp /home/jmc/demo4/target/classes:/root/.m2/repository/org/slf4j/jul-to-slf4j/2.0.4/jul-to-slf4j-2.0.4.jar:/root/.m2/repository/org/springframework/boot/spring-boot-starter-json/3.0.0/spring-boot-starter-json-3.0.0.jar:/root/.m2/repository/ch/qos/logback/logback-classic/1.4.5/logback-classic-1.4.5.jar:/root/.m2/repository/org/springframework/boot/spring-boot-starter-web/3.0.0/spring-boot-starter-web-3.0.0.jar:/root/.m2/repository/com/alibaba/nacos/nacos-auth-plugin/2.2.1-RC/nacos-auth-plugin-2.2.1-RC.jar:/root/.m2/repository/org/springframework/spring-beans/6.0.2/spring-beans-6.0.2.jar:/root/.m2/repository/org/apache/tomcat/embed/tomcat-embed-el/10.1.1/tomcat-embed-el-10.1.1.jar:/root/.m2/repository/commons-codec/commons-codec/1.15/commons-codec-1.15.jar:/root/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.14.1/jackson-core-2.14.1.jar:/root/.m2/repository/org/apache/logging/log4j/log4j-api/2.19.0/log4j-api-2.19.0.jar:/root/.m2/repository/org/springframework/spring-expression/6.0.2/spring-expression-6.0.2.jar:/root/.m2/repository/org/springframework/spring-webmvc/6.0.2/spring-webmvc-6.0.2.jar:/root/.m2/repository/org/springframework/boot/spring-boot/3.0.0/spring-boot-3.0.0.jar:/root/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/10.1.1/tomcat-embed-core-10.1.1.jar:/root/.m2/repository/org/springframework/spring-aop/6.0.2/spring-aop-6.0.2.jar:/root/.m2/repository/com/alibaba/nacos/nacos-encryption-plugin/2.2.1-RC/nacos-encryption-plugin-2.2.1-RC.jar:/root/.m2/repository/com/alibaba/nacos/nacos-client/2.2.1-RC/nacos-client-2.2.1-RC.jar:/root/.m2/repository/org/apache/httpcomponents/httpcore-nio/4.4.15/httpcore-nio-4.4.15.jar:/root/.m2/repository/com/fasterxml/jackson/datatype/jackson-datatype-jdk8/2.14.1/jackson-datatype-jdk8-2.14.1.jar:/root/.m2/repository/io/prometheus/simpleclient_tracer_otel_agent/0.16.0/simpleclient_tracer_otel_agent-0.16.0.jar:/root/.m2/repository/org/springframework/cloud/spring-cloud-commons/4.0.0/spring-cloud-commons-4.0.0.jar:/root/.m2/repository/org/springframework/spring-web/6.0.2/spring-web-6.0.2.jar:/root/.m2/repository/io/prometheus/simpleclient_tracer_common/0.16.0/simpleclient_tracer_common-0.16.0.jar:/root/.m2/repository/io/prometheus/simpleclient/0.16.0/simpleclient-0.16.0.jar:/root/.m2/repository/org/apache/httpcomponents/httpclient/4.5.13/httpclient-4.5.13.jar:/root/.m2/repository/com/alibaba/cloud/spring-cloud-starter-alibaba-nacos-discovery/2022.0.0.0-RC1/spring-cloud-starter-alibaba-nacos-discovery-2022.0.0.0-RC1.jar:/root/.m2/repository/io/prometheus/simpleclient_tracer_otel/0.16.0/simpleclient_tracer_otel-0.16.0.jar:/root/.m2/repository/ch/qos/logback/logback-core/1.4.5/logback-core-1.4.5.jar:/root/.m2/repository/org/springframework/cloud/spring-cloud-context/4.0.0/spring-cloud-context-4.0.0.jar:/root/.m2/repository/jakarta/annotation/jakarta.annotation-api/2.1.1/jakarta.annotation-api-2.1.1.jar:/root/.m2/repository/com/fasterxml/jackson/core/jackson-annotations/2.14.1/jackson-annotations-2.14.1.jar:/root/.m2/repository/com/alibaba/cloud/spring-cloud-alibaba-commons/2022.0.0.0-RC1/spring-cloud-alibaba-commons-2022.0.0.0-RC1.jar:/root/.m2/repository/org/springframework/spring-core/6.0.2/spring-core-6.0.2.jar:/root/.m2/repository/com/fasterxml/jackson/module/jackson-module-parameter-names/2.14.1/jackson-module-parameter-names-2.14.1.jar:/root/.m2/repository/org/apache/tomcat/embed/tomcat-embed-websocket/10.1.1/tomcat-embed-websocket-10.1.1.jar:/root/.m2/repository/org/springframework/spring-jcl/6.0.2/spring-jcl-6.0.2.jar:/root/.m2/repository/org/springframework/boot/spring-boot-autoconfigure/3.0.0/spring-boot-autoconfigure-3.0.0.jar:/root/.m2/repository/org/springframework/boot/spring-boot-starter-tomcat/3.0.0/spring-boot-starter-tomcat-3.0.0.jar:/root/.m2/repository/com/fasterxml/jackson/datatype/jackson-datatype-jsr310/2.14.1/jackson-datatype-jsr310-2.14.1.jar:/root/.m2/repository/com/alibaba/spring/spring-context-support/1.0.11/spring-context-support-1.0.11.jar:/root/.m2/repository/org/apache/logging/log4j/log4j-to-slf4j/2.19.0/log4j-to-slf4j-2.19.0.jar:/root/.m2/repository/org/springframework/boot/spring-boot-starter/3.0.0/spring-boot-starter-3.0.0.jar:/root/.m2/repository/org/springframework/security/spring-security-crypto/6.0.0/spring-security-crypto-6.0.0.jar:/root/.m2/repository/org/springframework/boot/spring-boot-starter-logging/3.0.0/spring-boot-starter-logging-3.0.0.jar:/root/.m2/repository/org/apache/httpcomponents/httpcore/4.4.15/httpcore-4.4.15.jar:/root/.m2/repository/org/slf4j/slf4j-api/2.0.4/slf4j-api-2.0.4.jar:/root/.m2/repository/org/springframework/spring-context/6.0.2/spring-context-6.0.2.jar:/root/.m2/repository/io/micrometer/micrometer-observation/1.10.2/micrometer-observation-1.10.2.jar:/root/.m2/repository/org/yaml/snakeyaml/1.33/snakeyaml-1.33.jar:/root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.14.1/jackson-databind-2.14.1.jar:/root/.m2/repository/org/apache/httpcomponents/httpasyncclient/4.1.5/httpasyncclient-4.1.5.jar:/root/.m2/repository/io/micrometer/micrometer-commons/1.10.2/micrometer-commons-1.10.2.jar --no-fallback -H:Path=/home/jmc/demo4/target -H:Name=demo4
================================================================================================================GraalVM Native Image: Generating 'demo4' (executable)...
================================================================================================================Warning: Could not resolve io.netty.channel.socket.nio.NioServerSocketChannel for reflection configuration. Reason: java.lang.ClassNotFoundException: io.netty.channel.socket.nio.NioServerSocketChannel.
[1/7] Initializing...                                                                            (9.4s @ 0.31GB) Version info: 'GraalVM 22.3.0 Java 17 CE'
 Java version info: '17.0.5+8-jvmci-22.3-b08'
 C compiler: gcc (linux, x86_64, 11.3.0)
 Garbage collector: Serial GC
 1 user-specific feature(s)
 - org.springframework.aot.nativex.feature.PreComputeFieldFeature
The bundle named: org.apache.el.Messages, has not been found. If the bundle is part of a module, verify the bundle name is a fully qualified class name. Otherwise verify the bundle path is accessible in the classpath.
Field org.apache.commons.logging.LogAdapter#log4jSpiPresent set to true at build time
Field org.apache.commons.logging.LogAdapter#log4jSlf4jProviderPresent set to true at build time
Field org.apache.commons.logging.LogAdapter#slf4jSpiPresent set to true at build time
Field org.apache.commons.logging.LogAdapter#slf4jApiPresent set to true at build time
Field org.springframework.core.NativeDetector#imageCode set to true at build time
Field org.springframework.core.KotlinDetector#kotlinPresent set to false at build time
Field org.springframework.core.KotlinDetector#kotlinReflectPresent set to false at build time
Field org.springframework.format.support.DefaultFormattingConversionService#jsr354Present set to false at build time
Field org.springframework.cglib.core.AbstractClassGenerator#imageCode set to true at build time
Field org.springframework.boot.logging.java.JavaLoggingSystem$Factory#PRESENT set to true at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#romePresent set to false at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#jaxb2Present set to false at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#jackson2Present set to true at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#jackson2XmlPresent set to false at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#jackson2SmilePresent set to false at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#jackson2CborPresent set to false at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#gsonPresent set to false at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#jsonbPresent set to false at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#kotlinSerializationCborPresent set to false at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#kotlinSerializationJsonPresent set to false at build time
Field org.springframework.web.servlet.config.annotation.WebMvcConfigurationSupport#kotlinSerializationProtobufPresent set to false at build time
Field org.springframework.boot.logging.log4j2.Log4J2LoggingSystem$Factory#PRESENT set to false at build time
Field org.springframework.boot.logging.logback.LogbackLoggingSystem$Factory#PRESENT set to true at build time
Field org.springframework.cloud.bootstrap.TextEncryptorConfigBootstrapper#RSA_IS_PRESENT set to false at build time
Field org.springframework.web.servlet.view.InternalResourceViewResolver#jstlPresent set to false at build time
Field org.springframework.web.context.support.StandardServletEnvironment#jndiPresent set to true at build time
Field org.springframework.web.context.support.WebApplicationContextUtils#jsfPresent set to false at build time
Field org.springframework.web.context.request.RequestContextHolder#jsfPresent set to false at build time
Field org.springframework.context.event.ApplicationListenerMethodAdapter#reactiveStreamsPresent set to false at build time
Field org.springframework.boot.logging.logback.LogbackLoggingSystemProperties#JBOSS_LOGGING_PRESENT set to false at build time
Field org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter#jaxb2Present set to false at build time
Field org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter#jackson2Present set to true at build time
Field org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter#jackson2XmlPresent set to false at build time
Field org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter#jackson2SmilePresent set to false at build time
Field org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter#gsonPresent set to false at build time
Field org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter#jsonbPresent set to false at build time
Field org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter#kotlinSerializationCborPresent set to false at build time
Field org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter#kotlinSerializationJsonPresent set to false at build time
Field org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter#kotlinSerializationProtobufPresent set to false at build time
Field org.springframework.boot.autoconfigure.web.format.WebConversionService#JSR_354_PRESENT set to false at build time
Field org.springframework.core.ReactiveAdapterRegistry#reactorPresent set to false at build time
Field org.springframework.core.ReactiveAdapterRegistry#rxjava3Present set to false at build time
Field org.springframework.core.ReactiveAdapterRegistry#kotlinCoroutinesPresent set to false at build time
Field org.springframework.core.ReactiveAdapterRegistry#mutinyPresent set to false at build time
SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
Field org.springframework.web.servlet.mvc.method.annotation.ReactiveTypeHandler#isContextPropagationPresent set to false at build time
Field org.springframework.web.client.RestTemplate#romePresent set to false at build time
Field org.springframework.web.client.RestTemplate#jaxb2Present set to false at build time
Field org.springframework.web.client.RestTemplate#jackson2Present set to true at build time
Field org.springframework.web.client.RestTemplate#jackson2XmlPresent set to false at build time
Field org.springframework.web.client.RestTemplate#jackson2SmilePresent set to false at build time
Field org.springframework.web.client.RestTemplate#jackson2CborPresent set to false at build time
Field org.springframework.web.client.RestTemplate#gsonPresent set to false at build time
Field org.springframework.web.client.RestTemplate#jsonbPresent set to false at build time
Field org.springframework.web.client.RestTemplate#kotlinSerializationCborPresent set to false at build time
Field org.springframework.web.client.RestTemplate#kotlinSerializationJsonPresent set to false at build time
Field org.springframework.web.client.RestTemplate#kotlinSerializationProtobufPresent set to false at build time
Field org.springframework.web.servlet.support.RequestContext#jstlPresent set to false at build time
[2/7] Performing analysis...  [***********]                                                    (105.7s @ 1.58GB)
  18,216 (92.48%) of 19,698 classes reachable
  30,664 (68.78%) of 44,581 fields reachable
  90,657 (61.00%) of 148,606 methods reachable
     843 classes,   205 fields, and 3,909 methods registered for reflection
      64 classes,    70 fields, and    55 methods registered for JNI access
       4 native libraries: dl, pthread, rt, z
[3/7] Building universe...                                                                       (8.8s @ 1.60GB)
[4/7] Parsing methods...      [***]                                                              (6.8s @ 2.23GB)
[5/7] Inlining methods...     [****]                                                             (3.8s @ 1.84GB)
[6/7] Compiling methods...    [*******]                                                         (55.5s @ 2.28GB)
[7/7] Creating image...                                                                         (10.4s @ 2.19GB)
  38.23MB (48.53%) for code area:    58,807 compilation units
  37.43MB (47.50%) for image heap:  409,428 objects and 382 resources
   3.13MB ( 3.97%) for other data
  78.79MB in total
----------------------------------------------------------------------------------------------------------------
Top 10 packages in code area:                           Top 10 object types in image heap:
   1.64MB sun.security.ssl                                 8.47MB byte[] for code metadata
   1.11MB com.alibaba.nacos.shaded.com.google.protobuf     4.34MB java.lang.Class
   1.05MB java.util                                        3.98MB java.lang.String
 832.54KB java.lang.invoke                                 3.63MB byte[] for embedded resources
 718.00KB com.sun.crypto.provider                          3.44MB byte[] for java.lang.String
 540.44KB org.apache.catalina.core                         3.15MB byte[] for general heap data
 510.83KB java.lang                                        1.53MB com.oracle.svm.core.hub.DynamicHubCompanion
 499.61KB org.apache.tomcat.util.net                     975.30KB byte[] for reflection metadata
 490.43KB org.apache.coyote.http2                        796.93KB java.lang.String[]
 479.00KB java.util.concurrent                           736.08KB java.util.HashMap$Node
  30.03MB for 768 more packages                            5.93MB for 3371 more object types
----------------------------------------------------------------------------------------------------------------
                    9.8s (4.7% of total time) in 70 GCs | Peak RSS: 4.43GB | CPU load: 6.12
----------------------------------------------------------------------------------------------------------------
Produced artifacts:
 /home/jmc/demo4/target/demo4 (executable)
 /home/jmc/demo4/target/demo4.build_artifacts.txt (txt)
================================================================================================================
Finished generating 'demo4' in 3m 27s.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  03:30 min
[INFO] Finished at: 2023-01-01T18:30:37+08:00
[INFO] ------------------------------------------------------------------------

Recently, we have branched out the 2022.x branch. There is a lag in the organization of wiki documents, and the content of each version is not distinguished. It needs to be unified.

We need to provide a method to help enterprises realize the smooth migration of the large-scale Spring Cloud Alibaba microservice system IP address stack from IPv4 to IPv6. The specific method is to achieve migration through dual registration and double subscription. The specific migration steps of this solution are as follows:

1. First, upgrade the Spring Cloud Alibaba framework for all microservice applications in the system to enable them to have dual-stack address extraction and resolution functions.
2. Transform the IP address protocol stack of the host machine where some microservices in the system are located, so that it supports dual-stack IPv4 and IPv6 addresses at the same time.
3. The dual-stack address extraction module in the microservice application modified in step 2 extracts the dual-stack addresses in the application host, and registers the dual-stack addresses to the registration center through the service registration module.
4. Consumers subscribe to the dual-stack IPv4 and IPv6 addresses of a service in the registration center, and compare the address stack types supported by the host through the dual-stack address resolution module in the application. If the host only supports IPv4, use The provider’s IPv4 address initiates a service call; if only IPv6 is supported or dual-stack is supported at the same time, the provider’s IPv6 address is used to initiate a service call. If the call fails, it is best to use the IPv4 address to retry.
5. When all Spring Cloud microservices in the system have completed supporting the IPv6 address stack, gradually close the IPv4 address stack for all application hosts, thereby smoothly completing the migration of the large-scale microservice system from the IPv4 address stack to the IPv6 address stack .

IPv4地址向IPv6地址迁移方案

我们需要提供一种帮助企业实现大规模Spring Cloud Alibaba微服务系统IP地址栈从IPv4平滑迁移到IPv6的方法，具体方法就是双注册双订阅实现迁移，该方案的具体迁移步骤：

1. 首先对所有的系统中的微服务应用进行Spring Cloud Alibaba框架升级，让其具备双栈地址提取和解析功能。
2. 对系统中的部分微服务所在宿主机进行IP地址协议栈改造，让其同时支持双栈IPv4和IPv6地址。
3. 经过步骤2改造的微服务应用中的双栈地址提取模块，提取应用宿主机中的双栈地址，并通过服务注册模块，将双栈地址都注册到注册中心。
4. 消费者订阅注册中心中的某个服务的双栈IPv4和IPv6地址，通过应用中的双栈地址解析模块，比对宿主机所支持的地址栈类型，如果宿主机仅支持IPv4，则使用提供者的IPv4地址发起服务调用；如果仅支持IPv6或同时支持双栈，则用提供者的IPv6地址发起服务调用，调用失败最好能使用IPv4地址进行重试。
5. 当系统中的所有Spring Cloud微服务都完成支持IPv6地址栈的支持后，逐步对所有应用宿主机关闭IPv4地址栈，从而平滑完成大规模微服务系统从IPv4地址栈到IPv6地址栈的迁移。

In branch of 2.2.9.RELEASE and 2021.0.4.0, we provide the ability to register IPv6 address. but in relevant logic, we don't filter some invalid addresses now, such as link local address(fe80::c03a:5bff:fee7:5b55) or any local address. We should filter them.

Describe what this PR does / why we need it

1. 移除nacos-config-2.4.x-example模块
2. nacos-config-example 相关调整: a. 移除spring-cloud-starter-bootstrap依赖 , 默认不再使用bootstrap.yml方式配置 b. 移除nacos config shared-configs 和 extension-configs 2中配置写法 , 新版本使用spring.config.import方式引入配置

Hello Community,

We are very glad to announce that Spring Cloud Alibaba 2022.0.0.0-RC1 is released.

You can check detailed release notes here:

• Release notes: https://github.com/alibaba/spring-cloud-alibaba/releases/tag/2022.0.0.0-RC1
• Relevant article: https://mp.weixin.qq.com/s/R3CVyxnJoR3xi9mGeXG-0A

If there are no notable bugs, the RELEASE version will come within a week.

If you have any questions using this version, please report the issue on Github.

Best regards, Spring Cloud Alibaba Team