web-dev-qa-db-ja.com

Spring Cloud ConfigEureka-最初のアプローチが機能しない

Spring CloudEurekaマイクロサービスアプリケーションを開発しています。 Eurekaファーストのアプローチを介してサービスを構成サービスに接続したいと思います。マイクロサービスはdockerコンテナーとしてパッケージ化され、docker-composeを介してデプロイされます。アプリケーションは次の要素で構成されています。

  1. myapp-service-registry:Spring CloudEurekaで実装されたサービスレジストリサービス
  2. myapp-config-service:SpringCloud構成サービスサーバー
  3. myapp-service-test:Eurekaファーストのアプローチを介してこれに接続することにより、構成サービスから構成データを取得しようとするマイクロサービスの例。

以下に説明するように、構成サービスへの接続が失敗します。まず第一に、いくつかの構成データ:

これがmyapp-service-registryapplication.ymlです。

server:
  port: ${PORT:8761}

eureka:
  client:
    registerWithEureka: false
    fetchRegistry: false
  server:
    waitTimeInMsWhenSyncEmpty: 0

ここでmyapp-config-serviceapplication.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

構成サーバーとクライアントは、 https://github.com/spring-cloud-samples/testsconfigserver-eurekaおよびeureka-firstサンプルのように初期化されます。

myapp-config-servicebootstrap.ymlは次のとおりです。

spring:
    application:
        name: myapp-config-service
    cloud:
        config:
            discovery:
                enabled: true

そしてmyapp-service-testapplication.yml

eureka:
    client:
        serviceUrl:
            defaultZone: http://${SERVICE_REGISTRY_Host}:${SERVICE_REGISTRY_PORT}/eureka/
    instance:
        preferIpAddress: true

そしてmyapp-service-testbootstrap.yml

spring:
  application:
    name: myapp-service-test
  cloud:
    config:
      discovery:
        enabled: true
        serviceId: myapp-config-service

以下はdocker-compose.ymlです(env変数は起動時に実際の値に置き換えられます):

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ファーストのアプローチを実装しない場合(およびspring.cloud.config.uriをサービスのbootstrap.ymlに直接設定する場合)、サービスはEurekaに登録し、構成サーバーを見つけて正しく機能することに注意してください( Eurekaのダッシュボードで登録済みのサービスを確認し、構成プロパティが正しく読み取られていることを確認できます)。

6
chrx

Bootstrap.ymlのeurekaserviceUrl(およびconfigserverのサービスID)が必要です。

10
Dave Syer