Generator-jhipster: 404 error on gateway application, using EKS

Created on 9 May 2019 · 4Comments · Source: jhipster/generator-jhipster

Hi!

Overview of the issue

I'm trying to deploy an application (monolithic or microservices, doesn't matter) to EKS (this one for example: https://github.com/PierreBesson/jhispter-aks-demo/), but everytime I'm requesting the gateway application I'm getting a 404 error, no matter which URL i'm requesting. The problem is no there are no strange behaviours or logs, all the pods and services are UP:

The application will start in 0s...
The Class-Path manifest attribute in /app/libs/liquibase-core-3.5.5.jar referenced one or more files that do not exist: file:/app/libs/lib/snakeyaml-1.13.jar
08:35:00.832 [main] DEBUG org.springframework.boot.devtools.settings.DevToolsSettings - Included patterns for restart : []
08:35:00.836 [main] DEBUG org.springframework.boot.devtools.settings.DevToolsSettings - Excluded patterns for restart : [/spring-boot-actuator/target/classes/, /spring-boot-devtools/target/classes/, /spring-boot/target/classes/, /spring-boot-starter-[\w-]+/, /spring-boot-autoconfigure/target/classes/, /spring-boot-starter/target/classes/]
08:35:00.836 [main] DEBUG org.springframework.boot.devtools.restart.ChangeableUrls - Matching URLs for reloading : [file:/app/resources/, file:/app/classes/]

        ██╗ ██╗   ██╗ ████████╗ ███████╗   ██████╗ ████████╗ ████████╗ ███████╗
        ██║ ██║   ██║ ╚══██╔══╝ ██╔═══██╗ ██╔════╝ ╚══██╔══╝ ██╔═════╝ ██╔═══██╗
        ██║ ████████║    ██║    ███████╔╝ ╚█████╗     ██║    ██████╗   ███████╔╝
  ██╗   ██║ ██╔═══██║    ██║    ██╔════╝   ╚═══██╗    ██║    ██╔═══╝   ██╔══██║
  ╚██████╔╝ ██║   ██║ ████████╗ ██║       ██████╔╝    ██║    ████████╗ ██║  ╚██╗
   ╚═════╝  ╚═╝   ╚═╝ ╚═══════╝ ╚═╝       ╚═════╝     ╚═╝    ╚═══════╝ ╚═╝   ╚═╝

:: JHipster 🤓  :: Running Spring Boot 2.0.7.RELEASE ::
:: https://www.jhipster.tech ::

2019-05-09 08:35:10.443  INFO 1 --- [  restartedMain] com.jhipster.demo.store.StoreApp         : The following profiles are active: prod
2019-05-09 08:35:23.135  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Initializing Eureka in region us-east-1
2019-05-09 08:35:23.622  INFO 1 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using JSON encoding codec LegacyJacksonJson
2019-05-09 08:35:23.623  INFO 1 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using JSON decoding codec LegacyJacksonJson
2019-05-09 08:35:23.947  INFO 1 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using XML encoding codec XStreamXml
2019-05-09 08:35:23.947  INFO 1 --- [  restartedMain] c.n.d.provider.DiscoveryJerseyProvider   : Using XML decoding codec XStreamXml
2019-05-09 08:35:24.515  INFO 1 --- [  restartedMain] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:35:24.537  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Disable delta property : false
2019-05-09 08:35:24.538  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Single vip registry refresh property : null
2019-05-09 08:35:24.538  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Force full registry fetch : false
2019-05-09 08:35:24.538  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Application is null : false
2019-05-09 08:35:24.538  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Registered Applications size is zero : true
2019-05-09 08:35:24.538  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Application version is -1: true
2019-05-09 08:35:24.538  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Getting all instance registry info from the eureka server
2019-05-09 08:35:25.107  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : The response status is 200
2019-05-09 08:35:25.111  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Starting heartbeat executor: renew interval is: 10
2019-05-09 08:35:25.114  INFO 1 --- [  restartedMain] c.n.discovery.InstanceInfoReplicator     : InstanceInfoReplicator onDemand update allowed rate per min is 8
2019-05-09 08:35:25.120  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Discovery Client initialized at timestamp 1557390925118 with initial instances count: 5
2019-05-09 08:35:25.438  INFO 1 --- [  restartedMain] com.hazelcast.instance.AddressPicker     : [LOCAL] [dev] [3.9.4] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [10.0.59.189]
2019-05-09 08:35:25.438  INFO 1 --- [  restartedMain] com.hazelcast.instance.AddressPicker     : [LOCAL] [dev] [3.9.4] Prefer IPv4 stack is true.
2019-05-09 08:35:25.439  WARN 1 --- [  restartedMain] com.hazelcast.instance.AddressPicker     : [LOCAL] [dev] [3.9.4] Could not find a matching address to start with! Picking one of non-loopback addresses.
2019-05-09 08:35:25.443  INFO 1 --- [  restartedMain] com.hazelcast.instance.AddressPicker     : [LOCAL] [dev] [3.9.4] Picked [10.0.37.15]:5701, using socket ServerSocket[addr=/0.0.0.0,localport=5701], bind any local is true
2019-05-09 08:35:25.511  INFO 1 --- [  restartedMain] com.hazelcast.system                     : [10.0.37.15]:5701 [dev] [3.9.4] Hazelcast 3.9.4 (20180420 - b8001d5) starting at [10.0.37.15]:5701
2019-05-09 08:35:25.511  INFO 1 --- [  restartedMain] com.hazelcast.system                     : [10.0.37.15]:5701 [dev] [3.9.4] Copyright (c) 2008-2018, Hazelcast, Inc. All Rights Reserved.
2019-05-09 08:35:25.511  INFO 1 --- [  restartedMain] com.hazelcast.system                     : [10.0.37.15]:5701 [dev] [3.9.4] Configured Hazelcast Serialization version: 1
2019-05-09 08:35:26.040  INFO 1 --- [  restartedMain] c.h.s.i.o.impl.BackpressureRegulator     : [10.0.37.15]:5701 [dev] [3.9.4] Backpressure is disabled
2019-05-09 08:35:27.330  INFO 1 --- [  restartedMain] com.hazelcast.instance.Node              : [10.0.37.15]:5701 [dev] [3.9.4] Creating TcpIpJoiner
2019-05-09 08:35:27.717  INFO 1 --- [  restartedMain] c.h.s.i.o.impl.OperationExecutorImpl     : [10.0.37.15]:5701 [dev] [3.9.4] Starting 2 partition threads and 3 generic threads (1 dedicated for priority tasks)
2019-05-09 08:35:27.723  INFO 1 --- [  restartedMain] c.h.internal.diagnostics.Diagnostics     : [10.0.37.15]:5701 [dev] [3.9.4] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
2019-05-09 08:35:27.730  INFO 1 --- [  restartedMain] com.hazelcast.core.LifecycleService      : [10.0.37.15]:5701 [dev] [3.9.4] [10.0.37.15]:5701 is STARTING
2019-05-09 08:35:27.757  INFO 1 --- [cached.thread-3] com.hazelcast.nio.tcp.TcpIpConnector     : [10.0.37.15]:5701 [dev] [3.9.4] Connecting to /10.0.59.189:5701, timeout: 0, bind-any: true
2019-05-09 08:35:27.761  INFO 1 --- [cached.thread-3] c.h.nio.tcp.TcpIpConnectionManager       : [10.0.37.15]:5701 [dev] [3.9.4] Established socket connection between /10.0.37.15:53267 and /10.0.59.189:5701
2019-05-09 08:35:34.775  INFO 1 --- [ration.thread-0] com.hazelcast.system                     : [10.0.37.15]:5701 [dev] [3.9.4] Cluster version set to 3.9
2019-05-09 08:35:34.778  INFO 1 --- [ration.thread-0] c.h.internal.cluster.ClusterService      : [10.0.37.15]:5701 [dev] [3.9.4] 

Members {size:2, ver:2} [
    Member [10.0.59.189]:5701 - 5133660f-9c5e-42e8-b5be-95677ac3d71f
    Member [10.0.37.15]:5701 - 5c873f09-016f-440f-bc6b-a6ec85bb404f this
]

2019-05-09 08:35:35.329  INFO 1 --- [tbeatExecutor-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_STORE/store:d795731965f7f61b110bf38e5e6e200a - Re-registering apps/STORE
2019-05-09 08:35:35.330  INFO 1 --- [tbeatExecutor-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_STORE/store:d795731965f7f61b110bf38e5e6e200a: registering service...
2019-05-09 08:35:35.510  INFO 1 --- [tbeatExecutor-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_STORE/store:d795731965f7f61b110bf38e5e6e200a - registration status: 204
2019-05-09 08:35:36.788  INFO 1 --- [  restartedMain] com.hazelcast.core.LifecycleService      : [10.0.37.15]:5701 [dev] [3.9.4] [10.0.37.15]:5701 is STARTED
2019-05-09 08:35:39.542  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:35:42.861  INFO 1 --- [  restartedMain] c.h.h.HazelcastCacheRegionFactory        : Starting up HazelcastCacheRegionFactory
2019-05-09 08:35:42.863  INFO 1 --- [  restartedMain] c.h.h.i.IHazelcastInstanceFactory        : Using existing HazelcastInstance [store].
2019-05-09 08:35:46.220  WARN 1 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2019-05-09 08:35:46.558  INFO 1 --- [  restartedMain] c.j.demo.store.config.WebConfigurer      : Web application configuration, using profiles: prod
2019-05-09 08:35:46.614  INFO 1 --- [  restartedMain] c.j.demo.store.config.WebConfigurer      : Web application fully configured
2019-05-09 08:35:52.125  WARN 1 --- [  restartedMain] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2019-05-09 08:35:54.543  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:35:57.227  INFO 1 --- [  restartedMain] com.netflix.discovery.DiscoveryClient    : Saw local status change event StatusChangeEvent [timestamp=1557390957227, current=UP, previous=STARTING]
2019-05-09 08:35:57.231  INFO 1 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_STORE/store:d795731965f7f61b110bf38e5e6e200a: registering service...
2019-05-09 08:35:57.339  INFO 1 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_STORE/store:d795731965f7f61b110bf38e5e6e200a - registration status: 204
2019-05-09 08:35:57.630  INFO 1 --- [  restartedMain] com.jhipster.demo.store.StoreApp         : Started StoreApp in 56.712 seconds (JVM running for 58.308)
2019-05-09 08:35:57.644  INFO 1 --- [  restartedMain] com.jhipster.demo.store.StoreApp         : 
----------------------------------------------------------
    Application 'store' is running! Access URLs:
    Local:      http://localhost:8080/
    External:   http://10.0.37.15:8080/
    Profile(s):     [prod]
----------------------------------------------------------
2019-05-09 08:35:57.644  INFO 1 --- [  restartedMain] com.jhipster.demo.store.StoreApp         : 
----------------------------------------------------------
    Config Server:  Connected to the JHipster Registry running in Kubernetes
----------------------------------------------------------
2019-05-09 08:35:58.713  INFO 1 --- [.IO.thread-in-0] com.hazelcast.nio.tcp.TcpIpConnection    : [10.0.37.15]:5701 [dev] [3.9.4] Connection[id=1, /10.0.37.15:53267->/10.0.59.189:5701, endpoint=[10.0.59.189]:5701, alive=false, type=MEMBER] closed. Reason: Connection closed by the other side
2019-05-09 08:35:58.717  INFO 1 --- [cached.thread-4] com.hazelcast.nio.tcp.TcpIpConnector     : [10.0.37.15]:5701 [dev] [3.9.4] Connecting to /10.0.59.189:5701, timeout: 0, bind-any: true
2019-05-09 08:35:58.718  INFO 1 --- [cached.thread-4] com.hazelcast.nio.tcp.TcpIpConnector     : [10.0.37.15]:5701 [dev] [3.9.4] Could not connect to: /10.0.59.189:5701. Reason: SocketException[Connection refused to address /10.0.59.189:5701]
2019-05-09 08:35:58.820  INFO 1 --- [cached.thread-4] com.hazelcast.nio.tcp.TcpIpConnector     : [10.0.37.15]:5701 [dev] [3.9.4] Connecting to /10.0.59.189:5701, timeout: 0, bind-any: true
2019-05-09 08:35:58.822  INFO 1 --- [cached.thread-4] com.hazelcast.nio.tcp.TcpIpConnector     : [10.0.37.15]:5701 [dev] [3.9.4] Could not connect to: /10.0.59.189:5701. Reason: SocketException[Connection refused to address /10.0.59.189:5701]
2019-05-09 08:35:58.930  INFO 1 --- [cached.thread-4] com.hazelcast.nio.tcp.TcpIpConnector     : [10.0.37.15]:5701 [dev] [3.9.4] Connecting to /10.0.59.189:5701, timeout: 0, bind-any: true
2019-05-09 08:35:58.931  INFO 1 --- [cached.thread-4] com.hazelcast.nio.tcp.TcpIpConnector     : [10.0.37.15]:5701 [dev] [3.9.4] Could not connect to: /10.0.59.189:5701. Reason: SocketException[Connection refused to address /10.0.59.189:5701]
2019-05-09 08:35:59.032  INFO 1 --- [cached.thread-4] com.hazelcast.nio.tcp.TcpIpConnector     : [10.0.37.15]:5701 [dev] [3.9.4] Connecting to /10.0.59.189:5701, timeout: 0, bind-any: true
2019-05-09 08:35:59.033  INFO 1 --- [cached.thread-4] com.hazelcast.nio.tcp.TcpIpConnector     : [10.0.37.15]:5701 [dev] [3.9.4] Could not connect to: /10.0.59.189:5701. Reason: SocketException[Connection refused to address /10.0.59.189:5701]
2019-05-09 08:35:59.033  WARN 1 --- [cached.thread-4] c.h.nio.tcp.TcpIpConnectionErrorHandler  : [10.0.37.15]:5701 [dev] [3.9.4] Removing connection to endpoint [10.0.59.189]:5701 Cause => java.net.SocketException {Connection refused to address /10.0.59.189:5701}, Error-Count: 5
2019-05-09 08:35:59.034  WARN 1 --- [cached.thread-4] c.h.i.cluster.impl.MembershipManager     : [10.0.37.15]:5701 [dev] [3.9.4] Member [10.0.59.189]:5701 - 5133660f-9c5e-42e8-b5be-95677ac3d71f is suspected to be dead for reason: No connection
2019-05-09 08:35:59.035  INFO 1 --- [cached.thread-4] c.h.i.cluster.impl.MembershipManager     : [10.0.37.15]:5701 [dev] [3.9.4] Starting mastership claim process...
2019-05-09 08:35:59.036  INFO 1 --- [cached.thread-4] c.h.i.cluster.impl.MembershipManager     : [10.0.37.15]:5701 [dev] [3.9.4] Local MembersView{version=2, members=[MemberInfo{address=[10.0.59.189]:5701, uuid=5133660f-9c5e-42e8-b5be-95677ac3d71f, liteMember=false}, MemberInfo{address=[10.0.37.15]:5701, uuid=5c873f09-016f-440f-bc6b-a6ec85bb404f, liteMember=false}]} with suspected members: [[10.0.59.189]:5701] and initial addresses to ask: []
2019-05-09 08:35:59.042  INFO 1 --- [cached.thread-2] c.h.internal.cluster.ClusterService      : [10.0.37.15]:5701 [dev] [3.9.4] 

Members {size:1, ver:3} [
    Member [10.0.37.15]:5701 - 5c873f09-016f-440f-bc6b-a6ec85bb404f this
]

2019-05-09 08:35:59.042  INFO 1 --- [cached.thread-2] c.h.i.cluster.impl.MembershipManager     : [10.0.37.15]:5701 [dev] [3.9.4] Mastership is claimed with: MembersView{version=3, members=[MemberInfo{address=[10.0.37.15]:5701, uuid=5c873f09-016f-440f-bc6b-a6ec85bb404f, liteMember=false}]}
2019-05-09 08:35:59.043  INFO 1 --- [cached.thread-3] c.h.t.TransactionManagerService          : [10.0.37.15]:5701 [dev] [3.9.4] Committing/rolling-back alive transactions of Member [10.0.59.189]:5701 - 5133660f-9c5e-42e8-b5be-95677ac3d71f, UUID: 5133660f-9c5e-42e8-b5be-95677ac3d71f
2019-05-09 08:35:59.045  INFO 1 --- [store.migration] c.h.i.p.InternalPartitionService         : [10.0.37.15]:5701 [dev] [3.9.4] Fetching most recent partition table! my version: 678
2019-05-09 08:35:59.045  INFO 1 --- [store.migration] c.h.i.p.InternalPartitionService         : [10.0.37.15]:5701 [dev] [3.9.4] Most recent partition table version: 678
2019-05-09 08:35:59.090  INFO 1 --- [store.migration] c.h.i.partition.impl.MigrationManager    : [10.0.37.15]:5701 [dev] [3.9.4] Partition balance is ok, no need to re-partition cluster data... 
2019-05-09 08:36:09.544  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:36:24.544  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:36:39.545  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:36:54.545  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:37:09.546  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:37:24.547  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:37:39.547  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:37:54.548  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:38:09.549  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:38:24.549  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:38:39.550  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:38:54.551  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:39:09.551  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:39:24.552  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:39:39.552  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:39:54.553  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:40:09.554  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:40:24.554  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:40:39.555  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:40:54.556  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:41:09.556  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:41:24.557  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:41:39.557  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:41:54.558  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:42:09.559  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:42:24.560  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:42:39.560  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:42:54.561  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:43:09.561  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:43:24.562  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:43:39.563  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:43:54.563  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:44:09.564  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:44:24.565  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:44:39.565  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:44:54.566  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:45:09.566  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:45:24.567  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:45:39.568  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:45:54.568  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:46:09.569  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:46:24.569  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:46:39.570  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:46:54.571  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:47:09.571  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:47:24.572  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:47:39.572  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:47:54.573  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:48:09.573  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:48:24.574  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:48:39.575  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:48:54.575  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:49:09.576  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:49:24.577  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:49:39.577  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:49:54.578  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:50:09.579  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:50:24.580  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:50:39.580  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:50:54.581  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:51:09.581  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:51:24.582  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:51:39.583  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:51:54.583  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:52:09.584  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:52:24.584  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:52:39.585  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:52:54.586  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:53:09.586  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:53:24.587  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:53:39.587  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:53:54.588  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:54:09.588  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:54:24.589  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:54:39.589  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:54:54.590  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:55:09.590  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:55:24.591  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:55:39.592  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:55:54.592  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:56:09.593  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:56:24.593  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:56:39.594  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:56:54.594  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:57:09.595  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:57:24.596  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:57:39.596  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:57:54.597  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:58:09.597  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:58:24.598  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:58:39.598  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:58:54.599  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:59:09.599  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:59:24.600  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:59:39.600  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 08:59:54.601  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:00:09.602  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:00:24.602  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:00:39.603  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:00:54.603  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:01:09.604  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:01:24.604  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:01:39.605  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:01:54.605  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:02:09.606  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:02:24.607  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:02:39.607  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:02:54.608  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:03:09.608  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:03:24.609  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:03:39.610  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:03:54.610  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:04:09.611  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:04:24.612  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:04:39.612  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:04:54.613  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:05:09.613  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:05:24.614  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:05:39.615  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:05:54.615  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:06:09.616  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:06:24.617  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:06:39.617  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:06:54.618  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:07:09.618  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:07:24.619  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:07:39.620  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:07:54.620  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:08:09.621  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:08:24.621  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:08:39.622  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:08:54.622  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:09:09.623  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:09:24.623  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:09:39.624  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:09:54.624  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:10:09.625  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:10:24.625  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:10:39.626  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:10:54.626  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:11:09.627  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:11:24.628  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:11:39.628  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:11:54.629  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:12:09.631  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:12:24.632  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:12:39.632  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:12:54.633  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:13:09.633  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:13:24.634  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:13:39.635  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:13:54.635  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:14:09.636  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:14:24.636  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:14:39.637  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:14:54.637  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:15:09.638  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:15:24.639  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:15:39.639  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:15:54.640  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:16:09.640  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:16:24.641  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:16:39.641  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:16:54.642  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:17:09.642  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:17:24.643  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:17:39.643  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:17:54.644  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:18:09.644  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:18:24.645  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:18:39.645  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:18:54.646  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:19:09.646  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:19:24.647  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:19:39.647  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:19:54.648  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:20:09.648  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:20:24.649  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:20:39.649  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:20:54.650  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:21:09.650  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:21:24.651  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:21:39.652  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:21:54.652  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:22:09.653  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:22:24.653  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:22:39.654  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:22:54.655  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:23:09.655  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:23:24.656  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:23:39.656  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:23:54.657  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:24:09.657  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:24:24.658  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:24:39.658  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:24:54.659  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:25:09.659  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:25:24.660  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:25:39.660  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:25:54.661  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:26:09.661  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:26:24.662  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:26:39.662  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:26:54.663  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:27:09.663  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:27:24.663  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:27:39.664  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:27:54.664  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:28:09.665  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:28:24.666  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:28:39.666  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:28:54.667  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2019-05-09 09:29:09.667  INFO 1 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration

And all the services/pods states:

NAME                                     READY   STATUS    RESTARTS   AGE
pod/accountancy-575745d6df-nktz5         1/1     Running   0          96m
pod/accountancy-mongodb-0                1/1     Running   0          96m
pod/crm-77d9f68955-jpnkc                 1/1     Running   0          96m
pod/crm-elasticsearch-648bb6b9c9-7x8pw   1/1     Running   0          96m
pod/crm-postgresql-5f944d7cdc-zlhhc      1/1     Running   0          96m
pod/jhipster-registry-0                  1/1     Running   0          96m
pod/jhipster-registry-1                  1/1     Running   0          96m
pod/store-594559bc6-hszrq                1/1     Running   0          89m
pod/store-mysql-6d9c475864-ptjn4         1/1     Running   0          96m

NAME                          TYPE           CLUSTER-IP       EXTERNAL-IP                                                              PORT(S)             AGE
service/accountancy           ClusterIP      172.20.169.132   <none>                                                                   8082/TCP            96m
service/accountancy-mongodb   ClusterIP      None             <none>                                                                   27017/TCP           96m
service/crm                   ClusterIP      172.20.241.196   <none>                                                                   8081/TCP            96m
service/crm-elasticsearch     ClusterIP      172.20.51.123    <none>                                                                   9200/TCP,9300/TCP   96m
service/crm-postgresql        ClusterIP      172.20.16.159    <none>                                                                   5432/TCP            96m
service/jhipster-registry     ClusterIP      None             <none>                                                                   8761/TCP            96m
service/store                 LoadBalancer   172.20.99.131    AMAZON_ELB_URL   8080:31443/TCP      96m
service/store-mysql           ClusterIP      172.20.126.0     <none>                                                                   3306/TCP            96m

NAME                                DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/accountancy         1         1         1            1           96m
deployment.apps/crm                 1         1         1            1           96m
deployment.apps/crm-elasticsearch   1         1         1            1           96m
deployment.apps/crm-postgresql      1         1         1            1           96m
deployment.apps/store               1         1         1            1           96m
deployment.apps/store-mysql         1         1         1            1           96m

NAME                                           DESIRED   CURRENT   READY   AGE
replicaset.apps/accountancy-575745d6df         1         1         1       96m
replicaset.apps/crm-77d9f68955                 1         1         1       96m
replicaset.apps/crm-elasticsearch-648bb6b9c9   1         1         1       96m
replicaset.apps/crm-postgresql-5f944d7cdc      1         1         1       96m
replicaset.apps/store-594559bc6                1         1         1       89m
replicaset.apps/store-76ff757bfb               0         0         0       96m
replicaset.apps/store-mysql-6d9c475864         1         1         1       96m

NAME                                   DESIRED   CURRENT   AGE
statefulset.apps/accountancy-mongodb   1         1         96m
statefulset.apps/jhipster-registry     2         2         96m

If i'm executing the curl command locally (inside the pod) I'm getting the same error. But I can clearly see the java process listenning on port 8080 and responding the 404:

$ k exec -it -n jhipster-demo-app store-594559bc6-hszrq sh 
$ curl localhost:8080
{"timestamp":"2019-05-09T09:26:22.996+0000","status":404,"error":"Not Found","message":"Not Found","path":"/"}
$ ps aux
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:5701            0.0.0.0:*               LISTEN      1/java
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      1/java
tcp        0      0 10.0.37.15:8080         10.0.57.41:52774        TIME_WAIT   -
tcp        0      0 10.0.37.15:33660        172.20.126.0:3306       ESTABLISHED 1/java
tcp        0      0 10.0.37.15:8080         10.0.57.41:52960        TIME_WAIT   -
tcp        0      0 10.0.37.15:8080         10.0.57.41:52694        TIME_WAIT   -
tcp        0      0 10.0.37.15:8080         10.0.57.41:52852        TIME_WAIT   -
tcp        0      0 10.0.37.15:33756        172.20.126.0:3306       ESTABLISHED 1/java
tcp        0      0 10.0.37.15:33656        172.20.126.0:3306       ESTABLISHED 1/java
tcp        1      0 10.0.37.15:34942        10.0.34.1:8761          CLOSE_WAIT  1/java
tcp        0      0 10.0.37.15:8080         10.0.57.41:52668        TIME_WAIT   -
tcp        0      0 10.0.37.15:33738        172.20.126.0:3306       ESTABLISHED 1/java
tcp        0      0 10.0.37.15:8080         10.0.57.41:52932        TIME_WAIT   -
tcp        0      0 10.0.37.15:33992        172.20.126.0:3306       ESTABLISHED 1/java
tcp        0      0 10.0.37.15:8080         10.0.57.41:52536        TIME_WAIT   -
tcp        0      0 10.0.37.15:33714        172.20.126.0:3306       ESTABLISHED 1/java
tcp        0      0 10.0.37.15:8080         10.0.57.41:52616        TIME_WAIT   -
tcp        0      0 10.0.37.15:33820        172.20.126.0:3306       ESTABLISHED 1/java
tcp        0      0 10.0.37.15:8080         10.0.57.41:52534        TIME_WAIT   -
tcp        0      0 10.0.37.15:33724        172.20.126.0:3306       ESTABLISHED 1/java
tcp        0      0 10.0.37.15:37550        10.0.34.1:8761          ESTABLISHED 1/java
tcp        0      0 10.0.37.15:33798        172.20.126.0:3306       ESTABLISHED 1/java
tcp        0      0 10.0.37.15:33426        172.20.126.0:3306       ESTABLISHED 1/java
tcp        0      0 10.0.37.15:8080         10.0.57.41:52776        TIME_WAIT   -

Another point (perhaps important, perhaps not): I'm storing my docker images in an ECR, and then I pull them on EKS to launch my application.

An interesting thing is that, if I try to deploy to GCP or locally, the application works greate. I'm talking about a microservices application for my example, but if I'm following the same steps with a monolithic application I get the same error.

a specific application here

Motivation for or Use Case

I'm getting a 404 without any logs explaining why.

Reproduce the error

Create a microservices project with jhipster (or you can use the same as me: https://github.com/PierreBesson/jhispter-aks-demo/).
I'm assuming you have an EKS cluster, or can create one.

I'm following this "procedure" to deploy my application on EKS:

$ cd accountancy && mvn package -Pprod jib:dockerBuild
$ cd ../crm && mvn package -Pprod jib:dockerBuild
$ cd ../store && mvn package -Pprod jib:dockerBuild
$ cd ..
$ jhipster import-jdl jhipster-demo.jdl
$ aws eks --region REGION update-kubeconfig --name CLUSTER_NAME
$ cd kubernetes && bash -e kubectl-apply.sh

Related issues

Suggest a Fix

JHipster Version(s)

6.0.0

JHipster configuration

I'm generating my application using the official docker image https://hub.docker.com/r/jhipster/jhipster/

INFO! Using JHipster version installed globally
INFO! Executing jhipster:info
INFO! Options: from-cli: true
Welcome to the JHipster Information Sub-Generator

##### **JHipster Version(s)**


/home/jhipster/app/jhispter-demo-app
`-- (empty)


cat: no such file or directory: .yo-rc.json

##### **JHipster configuration, a `.yo-rc.json` file generated in the root folder**


<details>
<summary>.yo-rc.json file</summary>
<pre>

</pre>
</details>


##### **JDL for the Entity configuration(s) `entityName.json` files generated in the `.jhipster` directory**

<details>
<summary>JDL entity definitions</summary>

<pre>

</pre>
</details>


##### **Environment and Tools**

openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)

git version 2.17.1

node: v10.15.3

npm: 6.9.0

yeoman: 2.0.6

yarn: 1.15.2

Entity configuration(s) `entityName.json` files generated in the `.jhipster` directory

jhipster-demo.jdl:

application {
  config {
    baseName store,
    applicationType gateway,
    packageName com.jhipster.demo.store,
    serviceDiscoveryType eureka,
    authenticationType jwt,
    prodDatabaseType mysql,
    cacheProvider hazelcast,
    buildTool maven,
    //messageBroker kafka,
    clientFramework angularX,
    enableSwaggerCodegen true,
    testFrameworks [protractor]
  }
  entities *
}
application {
  config {
    baseName crm,
    applicationType microservice,
    packageName com.jhipster.demo.crm,
    serviceDiscoveryType eureka,
    authenticationType jwt,
    prodDatabaseType postgresql,
    buildTool maven,
    searchEngine elasticsearch,
    serverPort 8081,
    skipUserManagement true
  }
  entities * except Invoice, Shipment
}
application {
  config {
    baseName accountancy,
    applicationType microservice,
    packageName com.jhipster.demo.accountancy,
    serviceDiscoveryType eureka,
    authenticationType jwt,
    databaseType mongodb,
    prodDatabaseType mongodb,
    devDatabaseType mongodb,
    cacheProvider no,
    enableHibernateCache false,
    buildTool maven,
    serverPort 8082,
    skipUserManagement true,
    testFrameworks [gatling]
  }
  entities Invoice, Shipment
}

entity Product {
    name String required
    description String
    price BigDecimal required min(0)
    size Size required
    image ImageBlob
}
enum Size {
    S, M, L, XL, XXL
}
entity Customer {
    firstName String required
    lastName String required
    gender Gender required
    email String required pattern(/^[^@\s]+@[^@\s]+\.[^@\s]+$/)
    phone String required
    addressLine1 String required
    addressLine2 String
    city String required
    country String required
}
enum Gender {
    MALE, FEMALE, OTHER
}
entity ProductOrder {
    placedDate Instant required
    status OrderStatus required
    code String required
    invoiceId String
}
enum OrderStatus {
    COMPLETED, PENDING, CANCELLED
}
entity OrderItem {
    quantity Integer required min(0)
    totalPrice BigDecimal required min(0)
    status OrderItemStatus required
}
enum OrderItemStatus {
    AVAILABLE, OUT_OF_STOCK, BACK_ORDER
}
relationship ManyToOne {
 OrderItem{product(name) required} to Product
}
relationship OneToMany {
   Customer{order} to ProductOrder{customer(email) required},
   ProductOrder{orderItem} to OrderItem{order(code) required} ,
}
service Product, Customer, ProductOrder, OrderItem with serviceClass
paginate Product, Customer, ProductOrder, OrderItem with pagination
/* Entities for Invoice microservice */
entity Invoice {
    code String required
    date Instant required
    details String
    status InvoiceStatus required
    paymentMethod PaymentMethod required
    paymentDate Instant required
    paymentAmount BigDecimal required
}
enum InvoiceStatus {
    PAID, ISSUED, CANCELLED
}
entity Shipment {
    trackingCode String
    date Instant required
    details String
}
enum PaymentMethod {
    CREDIT_CARD, CASH_ON_DELIVERY, PAYPAL
}
relationship OneToMany {
    Invoice{shipment} to Shipment{invoice(code) required}
}
service Invoice, Shipment with serviceClass
paginate Invoice, Shipment with pagination
microservice Invoice, Shipment with accountancy
microservice Customer, Product, ProductOrder, OrderItem with crm
deployment {
  deploymentType kubernetes,
  appsFolders [accountancy, crm, store],
  monitoring no,
  serviceDiscoveryType eureka,
  dockerRepositoryName "DOCKERNAME",
  kubernetesNamespace NAMESPACE,
  istio false,
  kubernetesServiceType LoadBalancer,
}

Don't forget to replace DOCKERNAME and NAMESPACE in the deployment section

Browsers and Operating System

The program is launched in a docker based on alpine. I get the error using Firefox and curl.

[x] Checking this box is mandatory (this is just to show you read everything)

needs-reproduction aws kubernetes

Source

PopiBrossard

Most helpful comment

Okta would be happy to sponsor AWS instances for JHipster. 🙂

On May 9, 2019, at 23:37, Pascal Grimaud notifications@github.com wrote:

@PopiBrossard : first of all, thanks for completing the issue with logs and information.

To be honest, we have difficulty to test and reproduce issues with AWS, as they didn't sponsor us. That's why the 2 sub generators AWS and AWS containers seems broken. There is 1 ticket opened since 7 months, and no one want to try to have a look or fix it.

About your issue, it looks like you used directly aws command, to deploy your applications to EKS. It is not something we provided so we can't help you here. As you said, it works well with GKE so it's not a JHipster bug. It's more related to your config with EKS. I suggest you to use Stackoverflow.

As already said in another ticket, we're looking maintainers for AWS sub generators. If you're interested, just tell us.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

mraible on 10 May 2019

❤3

All 4 comments

@PopiBrossard : first of all, thanks for completing the issue with logs and information.

To be honest, we have difficulty to test and reproduce issues with AWS, as they didn't sponsor us. That's why the 2 sub generators AWS and AWS containers seems broken. There is 1 ticket opened since 7 months, and no one want to try to have a look or fix it.

About your issue, it looks like you used directly aws command, to deploy your applications to EKS. It is not something we provided so we can't help you here. As you said, it works well with GKE so it's not a JHipster bug. It's more related to your config with EKS. I suggest you to use Stackoverflow.

As already said in another ticket, we're looking maintainers for AWS sub generators. If you're interested, just tell us.

pascalgrimaud on 10 May 2019

Okta would be happy to sponsor AWS instances for JHipster. 🙂

On May 9, 2019, at 23:37, Pascal Grimaud notifications@github.com wrote:

@PopiBrossard : first of all, thanks for completing the issue with logs and information.

To be honest, we have difficulty to test and reproduce issues with AWS, as they didn't sponsor us. That's why the 2 sub generators AWS and AWS containers seems broken. There is 1 ticket opened since 7 months, and no one want to try to have a look or fix it.

About your issue, it looks like you used directly aws command, to deploy your applications to EKS. It is not something we provided so we can't help you here. As you said, it works well with GKE so it's not a JHipster bug. It's more related to your config with EKS. I suggest you to use Stackoverflow.

As already said in another ticket, we're looking maintainers for AWS sub generators. If you're interested, just tell us.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

mraible on 10 May 2019

❤3

@pascalgrimaud given the huge engagement of Ippon with AWS, there should be something doable on that side.

jdubois on 10 May 2019

@pascalgrimaud thanks for your response and your advice.

After updating the project I was using (the example I gave you wasn't using the latest version of jhipster), the bug disappear. I should have a look at the changelog to completely understand why, but the bug is gone.

Just to clarify, I'm not really using an aws command to deploy to EKS. The real deployment is the bash -e kubectl-apply.sh. The aws command is just a way to generate ~/.aws/config file (to permit distant access to the EKS cluster, and so on executing kubectl commands).
In fact I'm just reporting here (and I'm sorry if it wasn't very clear ^^') the lack of logs. Even in debug mode nothing is said about my 404. I was pretty sure it was the way I was implementing the application that cause this issue, but I had no clue about the reason why it was happening.

As far as I know, you're not supporting older version of Jhipster, in this case I can close this issue.

PopiBrossard on 10 May 2019

Was this page helpful?

0 / 5 - 0 ratings

Related issues

I can not log in

frantzynicolas · 3Comments

Do we need JhiLanguageController?

marcelinobadin · 3Comments

Using includeAll tag in master.xml

chegola · 4Comments

Auto Rebase Action

SudharakaP · 3Comments

Update Redis to 6.0.x

DanielFran · 3Comments

Generator-jhipster: 404 error on gateway application, using EKS

Overview of the issue

Motivation for or Use Case

Reproduce the error

Related issues

Suggest a Fix

JHipster Version(s)

JHipster configuration

Entity configuration(s) entityName.json files generated in the .jhipster directory

Browsers and Operating System

Most helpful comment

All 4 comments

Related issues

Entity configuration(s) `entityName.json` files generated in the `.jhipster` directory