Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different behavior between Maven and Gradle #31

Open
TimHess opened this issue Aug 15, 2018 · 0 comments
Open

Different behavior between Maven and Gradle #31

TimHess opened this issue Aug 15, 2018 · 0 comments

Comments

@TimHess
Copy link

TimHess commented Aug 15, 2018

Hello,

When starting this application with mvn spring-boot:run, it looks for a config server at http://localhost:8888. The result on first run is a failure, with the Eureka server failing to start. Starting via Gradle does not appear to look for a config server at that address and starts without a problem.

I started a spring cloud config server, then started this Eureka server and since then Eureka will start just fine, even if that config server isn't running anymore.

Is it expected for this server to be fully operational without a config server? Should a first-time run of this application require a config server?

Thanks,
Tim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant