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

2nd
Feb 2016
Fabian Wallwitz
@cforce
Feb 02 2016 12:45
@FeignClient(name = "hello", fallback = HystrixClientFallback.class) seems not to be supported any more?
Dave Syer
@dsyer
Feb 02 2016 12:46
Says who?
Fabian Wallwitz
@cforce
Feb 02 2016 12:47
it look like .. i am using M4 (think so) an the anotations attribute is not there
1.1.0.M4
Fabian Wallwitz
@cforce
Feb 02 2016 12:50
spring-cloud-netflix-core-1.1.0.M4.jar org.springframework.cloud.netflix.feign.FeignClient -> no "fallback" ..
strange
which version is "http://cloud.spring.io/spring-cloud-netflix/spring-cloud-netflix.html" based on? .. i thought 1.0.7
its not there
is it latest snapshot onyl .. so the documentation is trunk based?
Fabian Wallwitz
@cforce
Feb 02 2016 13:48
shall i report this as Bug? Linking of "reference of " 1.0.7 on the hp goes to html side which says "fallback" is supported .. for 1.0.7.RELEASE i even can't find a TAG on github..
in 1.0.6.RELEASE ist not included either .. the feature seems to be 1 month old..Netflix/feign#298
Dave Syer
@dsyer
Feb 02 2016 14:01
The individual projects don't have links to old documentation
the top level spring-cloud does
You can raise an issue if you like
Fabian Wallwitz
@cforce
Feb 02 2016 14:21
Am i right, that there is absolutly NO approach to configure hystrix on 1.0.7 base?
try to ind any documentation /example howto use feignHystrixBuilder in the Configuration.class of @FeignClient
would it be ok to use standard @HystrixCommand in FeignClient which extendings the MvcInterface.. therfore overload the interface method and add the @HystrixCommand anotation..
Dave Syer
@dsyer
Feb 02 2016 14:30
Yes that is correct
Feign did not support it then
I don't know what happens when you add @HystrixCommand to a @FeignClient (never tried it)
Fabian Wallwitz
@cforce
Feb 02 2016 14:32
There must be a best pratice .. else it would mean Feign does not support having resilient design..? The deocumentazion does "linking" between Ribbon and Feign ..but its unclear how this gonnna work..
Dave Syer
@dsyer
Feb 02 2016 14:34
I guess
Did you try it and it didn't work?
Fabian Wallwitz
@cforce
Feb 02 2016 14:36
i will try
Dave Syer
@dsyer
Feb 02 2016 14:38
I guess that's the answer then
Fabian Wallwitz
@cforce
Feb 02 2016 14:40
i am not sure if ethere is "a answer" .. but look like i am not alone with my questionsmarks..
Dave Syer
@dsyer
Feb 02 2016 14:41
The answer is there: in Spring Cloud Netflix 1.0 you need to wrap your calls to a feign client with hystrix explicitly.
It's just an extra layer in your dependencies
1.1 makes it a bit simpler to configure but it's not going to be any different functionally
Fabian Wallwitz
@cforce
Feb 02 2016 14:42
ok .. sry for bothering .. is there any example with the 1.0 approach ..
Dave Syer
@dsyer
Feb 02 2016 14:42
There are plenty of examples of using @HystrixCommand
Fabian Wallwitz
@cforce
Feb 02 2016 14:43
ah .. ok
i think its cleat now tx.
lewis-ing
@lewis-ing
Feb 02 2016 14:45
@dsyer
When I started 2 Eureka service and one Eureka service called One service,one Eureka service called Two service
And the next I will start clients application and connect One Service,
I shutdown One service,It's does not support fail-over to Two Service
What should I do?
Can you tell me how to solve this problem? thx
Dave Syer
@dsyer
Feb 02 2016 14:49
How did you configure your clients?
I.e. the eureka.client.*
lewis-ing
@lewis-ing
Feb 02 2016 14:49
no,I only configure the ip of the Eureka service
Your meaning needs to be configured eureka.client.*?
Dave Syer
@dsyer
Feb 02 2016 14:50
Of course
lewis-ing
@lewis-ing
Feb 02 2016 14:50
ok,thx, I will try it
Dave Syer
@dsyer
Feb 02 2016 14:51
eureka.client.serviceUrl in particular I guess
lewis-ing
@lewis-ing
Feb 02 2016 14:54
  client:
    serviceUrl:
      defaultZone: http://127.0.0.1:8761/eureka/,http://127.0.0.1:8762/eureka/
this is before configure
you means eureka: client: serviceUrl:*
Dave Syer
@dsyer
Feb 02 2016 14:56
That should work
(assuming there is a "eureka" in there somewhere)
lewis-ing
@lewis-ing
Feb 02 2016 14:56
yes,It's work,but I shutdown one service,I got error info
Dave Syer
@dsyer
Feb 02 2016 14:57
Does it look like an error or just logs?
lewis-ing
@lewis-ing
Feb 02 2016 14:59
hold on
41284: WARN DiscoveryClient - Can't get a response from http://127.0.0.1:8761/eureka/apps/delta com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused: connect at com.sun.jersey.client.apache4.ApacheHttpClient4Handler.handle(ApacheHttpClient4Handler.java:184) ~[jersey-apache-client4-1.11.jar:1.11] at com.sun.jersey.api.client.filter.GZIPContentEncodingFilter.handle(GZIPContentEncodingFilter.java:120) ~[jersey-client-1.13.jar:1.13] at com.netflix.discovery.EurekaIdentityHeaderFilter.handle(EurekaIdentityHeaderFilter.java:28) ~[eureka-client-1.1.147.jar:1.1.147] at com.sun.jersey.api.client.Client.handle(Client.java:648) ~[jersey-client-1.13.jar:1.13] at com.sun.jersey.api.client.WebResource.handle(WebResource.java:680) ~[jersey-client-1.13.jar:1.13] at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) ~[jersey-client-1.13.jar:1.13] at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:507) ~[jersey-client-1.13.jar:1.13] at com.netflix.discovery.DiscoveryClient.getUrl(DiscoveryClient.java:1567) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.makeRemoteCall(DiscoveryClient.java:1122) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.makeRemoteCall(DiscoveryClient.java:1060) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.getAndUpdateDelta(DiscoveryClient.java:869) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.fetchRegistry(DiscoveryClient.java:748) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.access$1400(DiscoveryClient.java:105) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient$CacheRefreshThread.run(DiscoveryClient.java:1723) [eureka-client-1.1.147.jar:1.1.147] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_51] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_51] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_51] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
It's error info
Dave Syer
@dsyer
Feb 02 2016 15:03
It's a warning
not an error
lewis-ing
@lewis-ing
Feb 02 2016 15:04
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused: connect at com.sun.jersey.client.apache4.ApacheHttpClient4Handler.handle(ApacheHttpClient4Handler.java:184) ~[jersey-apache-client4-1.11.jar:1.11] at com.sun.jersey.api.client.filter.GZIPContentEncodingFilter.handle(GZIPContentEncodingFilter.java:120) ~[jersey-client-1.13.jar:1.13] at com.netflix.discovery.EurekaIdentityHeaderFilter.handle(EurekaIdentityHeaderFilter.java:28) ~[eureka-client-1.1.147.jar:1.1.147] at com.sun.jersey.api.client.Client.handle(Client.java:648) ~[jersey-client-1.13.jar:1.13] at com.sun.jersey.api.client.WebResource.handle(WebResource.java:680) ~[jersey-client-1.13.jar:1.13] at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) ~[jersey-client-1.13.jar:1.13] at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:507) ~[jersey-client-1.13.jar:1.13] at com.netflix.discovery.DiscoveryClient.getUrl(DiscoveryClient.java:1567) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.makeRemoteCall(DiscoveryClient.java:1122) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.makeRemoteCall(DiscoveryClient.java:1060) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.getAndUpdateDelta(DiscoveryClient.java:869) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.fetchRegistry(DiscoveryClient.java:748) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient.access$1400(DiscoveryClient.java:105) [eureka-client-1.1.147.jar:1.1.147] at com.netflix.discovery.DiscoveryClient$CacheRefreshThread.run(DiscoveryClient.java:1723) [eureka-client-1.1.147.jar:1.1.147] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_51] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_51] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_51]
I got exception info from the console of the eclilpse
Dave Syer
@dsyer
Feb 02 2016 15:04
Look at the log level ("WARN")
lewis-ing
@lewis-ing
Feb 02 2016 15:06

```<configuration scan="true" scanPeriod="30 seconds">

<contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator">
    <resetJUL>true</resetJUL>
</contextListener>

<!-- To enable JMX Management -->
<jmxConfigurator/>

<appender name="console" class="ch.qos.logback.core.ConsoleAppender">
    <encoder>
        <pattern>${PID}: %-5level %logger{0} - %msg%n</pattern>
    </encoder>
</appender>

<!-- Specify logging levels -->
<logger name="org.springframework" level="warn"/>
 <logger name="org.hibernate" level="warn"/>

<root level="info">
    <appender-ref ref="console"/>
</root>

</configuration>```

Your meaning that it does not affect the use of the current information service,
Dave Syer
@dsyer
Feb 02 2016 15:11
I mean that it's a WARN log
the author intended you to notice but not stop the world
The log is coming from netflix OSS code so I have no idea if the log is hiding an actual error. But I doubt it.
It would have been an ERROR
lewis-ing
@lewis-ing
Feb 02 2016 15:16
I guess if all the client services are running, it should be warning information that not affect running
if other client service don't work,that info should be error from netflix OSS
Thanks @dsyer
pradeepkusingh
@pradeepkusingh
Feb 02 2016 21:03
@dsyer - do we have any date for brixton GA release ?
Spencer Gibb
@spencergibb
Feb 02 2016 21:05
Q1 is what we are currenlty committed to. We are dependent on another team for one of our dependencies, we have to release after they do. Hopefully earlier than later.
pradeepkusingh
@pradeepkusingh
Feb 02 2016 21:05
Thanks Spencer
This message was deleted
Spencer Gibb
@spencergibb
Feb 02 2016 21:07
http://spinnaker.io/ yes it is. It’s not part of PCF, but spinnaker has CF support written by one of our engineers.
pradeepkusingh
@pradeepkusingh
Feb 02 2016 21:08
great Thanks :)