ava.lang.IllegalArgumentException: no server available
程序员文章站
2024-03-14 09:00:22
...
前言
在搭建SpringCloudAlibaba 的nacos时,项目搭建完成,可以构建成功,然后项目在启动时报错:
2020-04-25 11:04:11.304 ERROR 893 --- [TaskScheduler-1] o.s.c.a.nacos.discovery.NacosWatch : Error watching Nacos Service change
java.lang.IllegalArgumentException: no server available
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:354) ~[nacos-client-1.0.0.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:346) ~[nacos-client-1.0.0.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:294) ~[nacos-client-1.0.0.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.getServiceList(NamingProxy.java:276) ~[nacos-client-1.0.0.jar:na]
at com.alibaba.nacos.client.naming.net.NamingProxy.getServiceList(NamingProxy.java:252) ~[nacos-client-1.0.0.jar:na]
at com.alibaba.nacos.client.naming.NacosNamingService.getServicesOfServer(NacosNamingService.java:525) ~[nacos-client-1.0.0.jar:na]
at org.springframework.cloud.alibaba.nacos.discovery.NacosWatch.nacosServicesWatch(NacosWatch.java:127) ~[spring-cloud-alibaba-nacos-discovery-0.9.0.RELEASE.jar:0.9.0.RELEASE]
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_151]
at java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:308) ~[na:1.8.0_151]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java) ~[na:1.8.0_151]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[na:1.8.0_151]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[na:1.8.0_151]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_151]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_151]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_151]
分析原因
通过????错误信息我们首先看到时Nacos服务相关错误,因为我本地是刚搭建的环境,
经过漫长的百度查阅文档:
解决方案:
原来是版本冲突,我使用的是Springboot2.2.6RELEASE,跟SpringCloudAlibaba版本冲突,所以修改一下版本,就解决了问题以及配置文件里面写错了一个单词
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.1.7.RELEASE</version>
<relativePath/> <!-- lookup parent from repository -->
</parent>
<!--整合Springcloud-->
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-dependencies</artifactId>
<version>Greenwich.SR1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<!--整合Springcloud alibaba-->
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-alibaba-dependencies</artifactId>
<version>0.9.0.RELEASE</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
上一篇: Ubuntu 常用工具
推荐阅读
-
ava.lang.IllegalArgumentException: no server available
-
执行:kubectl get pods 错误:Unable to connect to the server: x509
-
go http client & server gzip数据压缩格式
-
Unable to connect to the server: dial tcp 192.168.0.132:16443: connect: no route to host解决
-
Error from server: Get https://xx:10250/containerLogs dial tcp 10250: connect: no route to host
-
浅谈PHP的$_SERVER[SERVER_NAME]
-
php+redis在实际项目中HTTP 500: Internal Server Error故障排除
-
浅谈PHP的$_SERVER[SERVER_NAME]
-
Eureka Server 增加安全用户认证 博客分类: spring boot 实践笔记 spring cloudeureka serversecurity
-
window server 2016 离线安装 .net framework 3.5