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

3rd
Feb 2017
Patrick Cornelißen
@pcornelissen
Feb 03 2017 07:22
is it safe to use spring-boot 1.5.x with Camden or should I wait?
Dave Syer
@dsyer
Feb 03 2017 07:23
There are some servlet/filter registrations that don't work (eureka server and sleuth)
There should be a Camden.SR5 in the next couple of days to fix that
It's pretty obvious if your app is affected (it won't start)
So suck it and see
Patrick Cornelißen
@pcornelissen
Feb 03 2017 07:54
if it’s only a couple of days I’ll wait for the SR5 :-)
Much to do, so I just shift some tasks around
thanks
Jeferson Cieza
@ForeverIsOurs
Feb 03 2017 19:59
Hello. I'm implementing Zuul in my project, but dont know how to make data aggregatioin to avoid multiple api calls. How can I do that? Help please!
Ion Pana
@pionlionzion_twitter
Feb 03 2017 21:48
Hey, I am using Consul for discovery and Spring cloud config.
My issue is that if I send a SIGTERM (normal termination) to a service, it will not de-register from Consul on shutdown.
The problem is caused by starting the service with these 2 flags:
--spring.cloud.config.enabled=true --spring.cloud.config.discovery.enabled=true. If I don't use Spring cloud config (eg: local config file) the service will de-register properly.
I tried to debug it and it looks like the main cause if that the ConsulLifecycle bean will be included in the bootstrap application context (AnnotationConfigApplicationContext), and
will be properly initialized, but on shutdown it looks like only the lifecycle beans in the embedded web application context get a proper shutdown (thus stop() never gets called on consul lifecycle bean). When I exclude the flags the bootstrap app context has no lifecycle beans, and consul lifecycle is included in the web app context, and everything works as expected.
Any suggestion on how to fix this?