史上巨坑eureka注册,出现TransportException异常

由于自己造轮子,所以踩了好久的坑,导致出现以下异常。

com.netflix.discovery.shared.transport.TransportException: Cannot execute request on any known server
	at com.netflix.discovery.shared.transport.decorator.RetryableEurekaHttpClient.execute(RetryableEurekaHttpClient.java:111) ~[eureka-client-1.6.2.jar:1.6.2]
	at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator.getApplications(EurekaHttpClientDecorator.java:134) ~[eureka-client-1.6.2.jar:1.6.2]
	at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator$6.execute(EurekaHttpClientDecorator.java:137) ~[eureka-client-1.6.2.jar:1.6.2]
	at com.netflix.discovery.shared.transport.decorator.SessionedEurekaHttpClient.execute(SessionedEurekaHttpClient.java:77) ~[eureka-client-1.6.2.jar:1.6.2]
	at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator.getApplications(EurekaHttpClientDecorator.java:134) ~[eureka-client-1.6.2.jar:1.6.2]
	at com.netflix.discovery.DiscoveryClient.getAndStoreFullRegistry(DiscoveryClient.java:1013) [eureka-client-1.6.2.jar:1.6.2]
	at com.netflix.discovery.DiscoveryClient.getAndUpdateDelta(DiscoveryClient.java:1055) [eureka-client-1.6.2.jar:1.6.2]
	at com.netflix.discovery.DiscoveryClient.fetchRegistry(DiscoveryClient.java:929) [eureka-client-1.6.2.jar:1.6.2]
	at com.netflix.discovery.DiscoveryClient.refreshRegistry(DiscoveryClient.java:1451) [eureka-client-1.6.2.jar:1.6.2]
	at com.netflix.discovery.DiscoveryClient$CacheRefreshThread.run(DiscoveryClient.java:1418) [eureka-client-1.6.2.jar:1.6.2]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_80]
	at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_80]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_80]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_80]
	at java.lang.Thread.run(Thread.java:745) [na:1.7.0_80]

从网上找遍了解决办法,最后也是没有解决。

eureka.client.registerWithEureka=false
eureka.client.fetchRegistry=false

最多的是在server端的配置文件中加入以上两句话(本来就加了),也是没用。


然后就觉得是client端的错误,没考虑是server端的错误,一直再查找client端出现的错误。

eureka.client.serviceUrl.defaultZone=http://localhost:8763/eureka/
feign.hystrix.enabled=true

一直再修改这两句话,要不就添加

security.basic.enabled=false

最终在client端没有解决问题。

然后又考虑是不是server端的问题,然后又改下面的几句话

eureka.instance.hostname=localhost
eureka.client.registerWithEureka=false
eureka.client.fetchRegistry=false
eureka.client.serviceUrl.defaultZone=http://${eureka.instance.hostname}:${server.port}/eureka/

结果还是没有改变client启动报错的问题。


就在想是不是服务器配置(port、contentPath、displayName)的问题,之前是这么写的

扫描二维码关注公众号,回复: 2927505 查看本文章

server端

server.display-name=pancake_eureka
server.port=8763(因为8761端口已经被占用了,所以做了修改)
server.context-path=/pancake
eureka.instance.hostname=localhost
eureka.client.registerWithEureka=false
eureka.client.fetchRegistry=false
eureka.client.serviceUrl.defaultZone=http://${eureka.instance.hostname}:${server.port}/eureka/

client端

eureka.client.serviceUrl.defaultZone=http://localhost:8763/eureka/
feign.hystrix.enabled=true
解决方案一、
将server端中的context-path修改成如下格式,这时候在启动就没问题了。
server.display-name=pancake_eureka
server.port=8763
server.context-path=/(或者不写这个配置,默认为/)

解决方案二、

将client端中的defaultZone做修改

eureka.client.serviceUrl.defaultZone=http://localhost:8763/pancake/eureka/
feign.hystrix.enabled=true

本以为在server端配置的eureka.client.serviceUrl.defaultZone和client端是同一个(无敌大坑),切忌没有contextPath的时候是一样的,如果有那么就要将server端配置的contextPath内容加到client端的defaultZone的访问路径端口号后面。


猜你喜欢

转载自blog.csdn.net/qq_35221138/article/details/81016171