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

29th
Oct 2015
Tommy Ludwig
@shakuzen
Oct 29 2015 05:36
In regards to the Spring Cloud Config server, is the final decision on searchPaths and related functionality that folders deeper than 1 level will not be supported?
For organizational purposes, I wanted to have groups of apps (top level folder) and then I was thinking a folder for each app inside a group folder. However, this is not possible currently, as far as I can tell.
The reason being that there will eventually (hopefully) be 100+ apps using the Spring Cloud Config server, and storing that in the root or even only one level deep folders doesn't seem clean enough to me.
Tommy Ludwig
@shakuzen
Oct 29 2015 05:51
I guess maybe separating the repositories by group is my best option. Right now we only have a few apps using it, so it isn't a problem yet. I suppose I'll look into it in the future when it becomes an issue.
turick
@turick
Oct 29 2015 22:07
if i'm using sleuth on all of my services and one of the services makes a feign client call to another service, should i expect that (span/trace -- not sure the right term) to be included in that feign client call?
turick
@turick
Oct 29 2015 23:06
a more important question... several services have mysteriously started producing the following error: java.lang.IllegalArgumentException: No ConfigurationProperties annotation found on 'org.springframework.cloud.bus.BusProperties'.
at org.springframework.util.Assert.notNull(Assert.java:115)
the services are using dependency management for Brixton.BUILD-SNAPSHOT and the dependency spring-cloud-starter-bus-amqp. the only way to really fix it is to remove the spring-cloud-starter-bus-amqp dependency
actually i lied... one of the services is not using the spring cloud parent and is pulling in each dependency under management -- my zuul service is putting spring-cloud-bus-parent in dependency management and using the starter-bus-amqp version 1.1.0.BUILD-SNAPSHOT and producing the error also
turick
@turick
Oct 29 2015 23:45
apparently the issue also trickles down to spring-cloud-sleuth-zipkin. i hope this wasn't something stupid i've done, but it's happening on multiple services that haven't changed. i was also getting the following error on our edge server when trying to access a new service:
Caused by: java.lang.NullPointerException: null
at org.springframework.cloud.sleuth.zipkin.ZipkinSpanListener.clientReceive(ZipkinSpanListener.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sorry, the root exception was this: com.netflix.zuul.exception.ZuulException: Filter threw Exception
at com.netflix.zuul.FilterProcessor.processZuulFilter(FilterProcessor.java:231)
at com.netflix.zuul.FilterProcessor.runFilters(FilterProcessor.java:161)
at com.netflix.zuul.FilterProcessor.postRoute(FilterProcessor.java:92)
it doesn't happen with every service, but it's still a new error that came from an existing deployment that hasn't changed.