These are chat archives for spring-cloud/spring-cloud

2nd
Mar 2016
Fairuz Wan Ismail
@wmfairuz
Mar 02 2016 06:10
Hi guys, I'm getting errors on the client not being able to send heartbeat. But Eureka just detects the client fine and it shows the client as "UP".
2016-03-02 06:01:40.635  WARN 1 --- [tbeatExecutor-0] c.n.d.s.t.d.RetryableEurekaHttpClient    : Request execution failure
2016-03-02 06:01:40.636 ERROR 1 --- [tbeatExecutor-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_USER/user:user:8240 - was unable to send heartbeat!

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.4.2.jar!/:1.4.2]
        at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator.sendHeartBeat(EurekaHttpClientDecorator.java:89) ~[eureka-client-1.4.2.jar!/:1.4.2]
        at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator$3.execute(EurekaHttpClientDecorator.java:92) ~[eureka-client-1.4.2.jar!/:1.4.2]
        at com.netflix.discovery.shared.transport.decorator.SessionedEurekaHttpClient.execute(SessionedEurekaHttpClient.java:77) ~[eureka-client-1.4.2.jar!/:1.4.2]
        at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator.sendHeartBeat(EurekaHttpClientDecorator.java:89) ~[eureka-client-1.4.2.jar!/:1.4.2]
        at com.netflix.discovery.DiscoveryClient.renew(DiscoveryClient.java:819) ~[eureka-client-1.4.2.jar!/:1.4.2]
        at com.netflix.discovery.DiscoveryClient$HeartbeatThread.run(DiscoveryClient.java:1375) [eureka-client-1.4.2.jar!/:1.4.2]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_66-internal]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_66-internal]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_66-internal]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_66-internal]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66-internal]
I'm using SB 1.3.1.RELEASE and Spring Cloud Brixton.BUILD-SNAPSHOT
Fairuz Wan Ismail
@wmfairuz
Mar 02 2016 06:27
Updating to 1.3.3 seems solves the issue
Kaleb Scholes
@kalebscholes
Mar 02 2016 21:28
Hey guys! I'm working on a set up using consul as a discovery/config server and so far everything is working fantastic but what's the preferred way of getting the config files (yaml in our case) initially loaded in consul?
Marcos Barbero
@marcosbarbero
Mar 02 2016 21:37
Hi guys, few days ago I was facing an issue trying to figure out how to enable OAuth2 on Spring Cloud Config Server/Client. Of course the server was not a problem at all but the clients had to know how to comunicate using the OAuth2 credentials.
@dsyer gave me some tips from Pivotal source to figure it out, so I just did an extension from spring-cloud-config-client with oauth2. It’s just a start, any advice will be welcomed.
The source can be found here https://github.com/marcosbarbero/spring-cloud-config-client-oauth2
Spencer Gibb
@spencergibb
Mar 02 2016 22:04
@kalebscholes not sure there is one yet, there’s a tool, but I haven’t tried it yet
Kaleb Scholes
@kalebscholes
Mar 02 2016 22:26
@spencergibb interesting.. thanks! I've just discovered git2consul are there other tools you can point me too?
Spencer Gibb
@spencergibb
Mar 02 2016 22:26
I think that is the one I’m thinking of