Closed Acris closed 7 years ago
Seems like this issue might belong in Spring Cloud Consul. @spencergibb thoughts?
It's actually a WARN, not ERROR, BTW
It's actually a bug in s-c-netflix when using zuul that triggers premature initialization. It has already been fixed in #1916. I ran this using Edgware snapshots and it is gone. It was a fairly invasive change, that's why I didn't put it in Dalston. We could chat about backporting.
Thanks for your reply, So, the next release will fix it?
It's already fixed in Edgware (unreleased). The question is whether or not to backport for Dalston.
Any update on this discussion ? May I cherry-pick this commit and submit a PR for Dalston (1.3.x) ?
I think this may have not made it to our list of items to discuss with the team, I will add it to this week's agenda.
Hello, I created a empty spring boot project for Zuul gateway, and then I added those dependencies:
Then, I added
@EnableZuulProxy
to my main application class, like this:Next step, I configured fetch configuration from spring cloud config server, this is my
bootstrap.yml
:When everything is ready, I started my application, but unfortunately, I got a error:
I Googled for it, I only found a seem issue: https://github.com/spring-cloud/spring-cloud-consul/issues/306
I tried change
@EnableZuulProxy
to@EnableZuulServer
, then this error disappeared, but I can't find out how to solved it if I need use@EnableZuulProxy
annotation.Can anyone help me? Thank you very much.