fix: 2022.x #3445 A bean for InetIPv6Utils that could not found at pr… #3694
Conversation
…d at project start up A bean for InetIPv6Utils could not be found at project start up when integrating Spring Cloud Config with Spring Cloud Alibaba Nacos Discovery.
|
|
| @@ -38,7 +39,7 @@ | |||
| @Configuration(proxyBeanMethods = false) | |||
| @ImportAutoConfiguration({ NacosDiscoveryAutoConfiguration.class, | |||
| NacosServiceAutoConfiguration.class, NacosDiscoveryClientConfiguration.class, | |||
| NacosReactiveDiscoveryClientConfiguration.class }) | |||
| NacosReactiveDiscoveryClientConfiguration.class, UtilIPv6AutoConfiguration.class }) | |||
There was a problem hiding this comment.
移除 UtilIPv6AutoConfiguration 配置类，将里面的配置移动到 NacosDiscoveryAutoConfiguration 可能会比较好一些
There was a problem hiding this comment.
按你的方案进行修改，应用启动一会儿就会闪退，原因是NacosServiceManager被创建出两个实例，其中一个实例的nacosDiscoveryProperties属性值为空，导致NPE异常闪退。
请问NacosServiceManager需要多实例吗？
There was a problem hiding this comment.
我这边基于 nacos-discovery-consumer-example 测试并未复现，移除 UtilIPv6AutoConfiguration 后，需要同时移除 META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports 里面相关的配置
There was a problem hiding this comment.
集成org.springframework.cloud:spring-cloud-starter-config就会出现异常。
UtilIPv6AutoConfiguration用到的地方移除了。
There was a problem hiding this comment.
我看了下 InetIPv6Utils 的引用，只有在 discovery 模块中用到，2022和2023版本目前在挺多项目中有集成，有可能是你项目中的一些个性化配置导致了这个问题
There was a problem hiding this comment.
在集成SpringCloud Config配置服务时客户端不启用其discovery能力，即spring.cloud.config.discovery.enabled=false 是可以正常启动的。
目前我们是把SpringCloud Config服务注册到Nacos，其他服务通过Nacos来发现配置服务。
spring.cloud.config.discovery.enabled=true
…oject start up
A bean for InetIPv6Utils could not be found at project start up when integrating Spring Cloud Config with Spring Cloud Alibaba Nacos Discovery.
Describe what this PR does / why we need it
Does this pull request fix one issue?
#3445
Describe how you did it
Describe how to verify it
Special notes for reviews