Spring Cloud Config Eureka-first 方法不起作用
Posted
技术标签:
【中文标题】Spring Cloud Config Eureka-first 方法不起作用【英文标题】:Spring Cloud Config Eureka-first approach not working 【发布时间】:2016-05-12 09:19:55 【问题描述】:我正在开发一个 Spring Cloud Eureka 微服务应用程序。我希望我的服务通过 Eureka-first 方法连接到配置服务。微服务被打包为 docker 容器并通过 docker-compose 部署。该应用程序由以下人员组成:
myapp-service-registry
:使用Spring Cloud Eureka实现的服务注册服务
myapp-config-service
:Spring Cloud 配置服务服务器
myapp-service-test
:一个示例微服务,它应该尝试通过 Eureka-first 方法连接到配置服务来获取其配置数据。
与配置服务的连接失败,如下所述。首先是一些配置数据:
这里是myapp-service-registry
的application.yml
:
server:
port: $PORT:8761
eureka:
client:
registerWithEureka: false
fetchRegistry: false
server:
waitTimeInMsWhenSyncEmpty: 0
这里是myapp-config-service
的application.yml
:
server:
port: $MYAPP_CONFIG_SERVICE_PORT:8888
spring:
cloud:
config:
server:
git:
uri: $MYAPP_CONFIG_SERVICE_GIT_URI
config:
name: myapp-config-service
# eureka service registry client
eureka:
client:
serviceUrl:
defaultZone: http://$SERVICE_REGISTRY_HOST:$SERVICE_REGISTRY_PORT/eureka/
instance:
preferIpAddress: true
配置服务器和客户端在configserver-eureka
和eureka-first
示例中初始化为https://github.com/spring-cloud-samples/tests:
myapp-config-service
的bootstrap.yml
是:
spring:
application:
name: myapp-config-service
cloud:
config:
discovery:
enabled: true
还有myapp-service-test
的application.yml
:
eureka:
client:
serviceUrl:
defaultZone: http://$SERVICE_REGISTRY_HOST:$SERVICE_REGISTRY_PORT/eureka/
instance:
preferIpAddress: true
还有myapp-service-test
的bootstrap.yml
:
spring:
application:
name: myapp-service-test
cloud:
config:
discovery:
enabled: true
serviceId: myapp-config-service
下面是docker-compose.yml
(环境变量在启动时被实际值替换):
myapp-service-registry:
image: myapp/myapp-service-registry:0.0.1
ports:
- $EUREKA_PORT:$EUREKA_PORT
# myapp-config-service
myapp-config-service:
image: myapp/myapp-config-service:0.0.1
volumes:
- $MYAPP_DATA_FOLDER/config:/var/opt/myapp/config
environment:
MYAPP_CONFIG_SERVICE_PORT: $MYAPP_CONFIG_SERVICE_PORT
SERVICE_REGISTRY_HOST: $MYAPP_STAGING_IP
SERVICE_REGISTRY_PORT: $EUREKA_PORT
MYAPP_CONFIG_SERVICE_GIT_URI: $MYAPP_CONFIG_SERVICE_GIT_URI
ports:
- $MYAPP_CONFIG_SERVICE_PORT:$MYAPP_CONFIG_SERVICE_PORT
# myapp-service-test
myapp-service-test:
image: myapp/myapp-service-test:0.0.1
environment:
SERVICE_REGISTRY_HOST: $MYAPP_STAGING_IP
SERVICE_REGISTRY_PORT: $EUREKA_PORT
ports:
- $MYAPP_SERVICE_TEST_TWO_PORT:8080
我可以通过将浏览器连接到 http://[...MACHINE-IP...]:8761/ 并查看 Eureka 仪表板来检查 Eureka 是否正常工作。同样,我测试配置服务是否正常工作并响应http:///[...MACHINE-IP...]:8888/myapp-config-service;另一方面,使用上述配置,myapp-service-test 在启动时会崩溃并显示以下日志:
-02-03 08:26:45.191 INFO 1 --- [ main] e.f.s.two.TestServiceApplication : Starting TestServiceApplication v0.0.1 on b1bc37422027 with PID 1 (/app.jar started by root in /)
2016-02-03 08:26:45.223 INFO 1 --- [ main] e.f.s.two.TestServiceApplication : No active profile set, falling back to default profiles: default
2016-02-03 08:26:45.448 INFO 1 --- [ main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@4d97e82d: startup date [Wed Feb 03 08:26:45 UTC 2016]; root of context hierarchy
2016-02-03 08:26:46.382 INFO 1 --- [ main] f.a.AutowiredAnnotationBeanPostProcessor : JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
2016-02-03 08:26:46.442 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'configurationPropertiesRebinderAutoConfiguration' of type [class org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$6b65138e] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2016-02-03 08:26:47.089 INFO 1 --- [ main] o.s.c.n.eureka.InstanceInfoFactory : Setting initial instance status as: STARTING
2016-02-03 08:26:48.231 INFO 1 --- [ main] c.n.d.provider.DiscoveryJerseyProvider : Using encoding codec LegacyJacksonJson
2016-02-03 08:26:48.237 INFO 1 --- [ main] c.n.d.provider.DiscoveryJerseyProvider : Using decoding codec LegacyJacksonJson
2016-02-03 08:26:49.171 INFO 1 --- [ main] c.n.d.provider.DiscoveryJerseyProvider : Using encoding codec LegacyJacksonJson
2016-02-03 08:26:49.171 INFO 1 --- [ main] c.n.d.provider.DiscoveryJerseyProvider : Using decoding codec LegacyJacksonJson
2016-02-03 08:26:49.496 INFO 1 --- [ main] com.netflix.discovery.DiscoveryClient : Disable delta property : false
2016-02-03 08:26:49.497 INFO 1 --- [ main] com.netflix.discovery.DiscoveryClient : Single vip registry refresh property : null
2016-02-03 08:26:49.497 INFO 1 --- [ main] com.netflix.discovery.DiscoveryClient : Force full registry fetch : false
2016-02-03 08:26:49.498 INFO 1 --- [ main] com.netflix.discovery.DiscoveryClient : Application is null : false
2016-02-03 08:26:49.502 INFO 1 --- [ main] com.netflix.discovery.DiscoveryClient : Registered Applications size is zero : true
2016-02-03 08:26:49.503 INFO 1 --- [ main] com.netflix.discovery.DiscoveryClient : Application version is -1: true
2016-02-03 08:26:49.503 INFO 1 --- [ main] com.netflix.discovery.DiscoveryClient : Getting all instance registry info from the eureka server
2016-02-03 08:26:49.720 WARN 1 --- [ main] com.netflix.discovery.DiscoveryClient : Can't get a response from http://localhost:8761/eureka/apps/
<...>
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused
at com.sun.jersey.client.apache4.ApacheHttpClient4Handler.handle(ApacheHttpClient4Handler.java:187) ~[jersey-apache-client4-1.19.jar!/:1.19]
at com.sun.jersey.api.client.filter.GZIPContentEncodingFilter.handle(GZIPContentEncodingFilter.java:123) ~[jersey-client-1.19.jar!/:1.19]
at com.netflix.discovery.EurekaIdentityHeaderFilter.handle(EurekaIdentityHeaderFilter.java:27) ~[eureka-client-1.3.4.jar!/:1.3.4]
<...>
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_66-internal]
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[na:1.8.0_66-internal]
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_66-internal]
<...>
2016-02-03 08:26:49.747 ERROR 1 --- [ main] com.netflix.discovery.DiscoveryClient : Can't contact any eureka nodes - possibly a security group issue?
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused
<...>
2016-02-03 08:26:49.770 ERROR 1 --- [ main] com.netflix.discovery.DiscoveryClient : DiscoveryClient_MYAPP-SERVICE-TEST/b1bc37422027:myapp-service-test - was unable to refresh its cache! status = java.net.ConnectException: Connection refused
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused
<...>
2016-02-03 08:26:49.785 WARN 1 --- [ main] com.netflix.discovery.DiscoveryClient : Using default backup registry implementation which does not do anything.
2016-02-03 08:26:49.810 INFO 1 --- [ main] com.netflix.discovery.DiscoveryClient : Starting heartbeat executor: renew interval is: 10
2016-02-03 08:26:49.818 INFO 1 --- [ main] c.n.discovery.InstanceInfoReplicator : InstanceInfoReplicator onDemand update allowed rate per min is 4
2016-02-03 08:26:50.443 WARN 1 --- [ main] lientConfigServiceBootstrapConfiguration : Could not locate configserver via discovery
java.lang.RuntimeException: No matches for the virtual host name :myapp-config-service
at com.netflix.discovery.DiscoveryClient.getNextServerFromEureka(DiscoveryClient.java:782) ~[eureka-client-1.3.4.jar!/:1.3.4]
at org.springframework.cloud.netflix.config.DiscoveryClientConfigServiceBootstrapConfiguration.refresh(DiscoveryClientConfigServiceBootstrapConfiguration.java:71) [spring-cloud-netflix-core-1.1.0.M3.jar!/:1.1.0.M3]
<...>
2016-02-03 08:26:50.470 INFO 1 --- [ main] e.f.s.two.TestServiceApplication : Started TestServiceApplication in 7.101 seconds (JVM running for 9.329)
. ____ _ __ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot :: (v1.3.1.RELEASE)
2016-02-03 08:26:50.773 INFO 1 --- [ main] c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at: http://localhost:8888
2016-02-03 08:26:51.015 WARN 1 --- [ main] c.c.c.ConfigServicePropertySourceLocator : Could not locate PropertySource: I/O error on GET request for "http://localhost:8888/myapp-service-test/default":Connection refused; nested exception is java.net.ConnectException: Connection refused
<...>
2016-02-03 08:26:54.856 ERROR 1 --- [pool-5-thread-1] com.netflix.discovery.DiscoveryClient : Can't contact any eureka nodes - possibly a security group issue?
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused
<...>
2016-02-03 08:26:57.272 WARN 1 --- [ main] ationConfigEmbeddedWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'testTwoServiceController': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: java.lang.String myapp.services.two.TestServiceController.message; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'message' in string value "$message"
2016-02-03 08:26:57.281 INFO 1 --- [ main] o.apache.catalina.core.StandardService : Stopping service Tomcat
2016-02-03 08:26:57.299 ERROR 1 --- [ main] o.s.boot.SpringApplication : Application startup failed
请注意,如果我没有实现 Eureka-first 方法(并直接在服务的bootstrap.yml
中设置 spring.cloud.config.uri),服务将注册到 Eureka,找到配置服务器并正常工作(我可以在 Eureka 的仪表板中看到注册的服务,并且可以检查配置属性是否被正确读取)。
【问题讨论】:
你需要 bootstrap.yml 中的 eureka serviceUrl 不是吗(以及配置服务器的服务 ID)? 就是这样!通过将 myapp-service-test 中的 eureka 配置从 application.yml 移动到 bootstrap.yml,服务可以正确找到所有内容。想想看,还挺合乎逻辑的……我错过了,因为在测试服务的第一个版本(没有配置服务器)中,如果在 application.yml 中配置,eureka 注册就可以工作。然后我只是没有注意到必须将相同的内容移至 boostrap.yml,因为我也在那里配置了 spring.cloud.config.discovery。非常感谢, 你使用了哪个版本的 Spring 来实现这个功能?我可以让它与 Spring Boot:1.3.1.RELEASE 和 Cloud:Brixton.BUILD-SNAPSHOT 一起使用,但是否有一个有效的 RELEASE(不是 SNAPSHOT)设置? 【参考方案1】:您需要 bootstrap.yml 中的 eureka serviceUrl(以及 configserver 的服务 id)。
【讨论】:
以上是关于Spring Cloud Config Eureka-first 方法不起作用的主要内容,如果未能解决你的问题,请参考以下文章