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
Error with EurekaServer in standalone mode. #120
Comments
As far as I know that's harmless. I think it's just a sign that the Eureka client part of the server hasn't started up properly yet (it takes a while). Unfortunately the error is logged by third party code (Netflix) so it's not possible to suppress it without just switching off logging for that channel (which is what I usually do). |
Thanks Dave. One other quick Eureka related question if I could. I noticed that the client connects but it shows as registered but unavailable rather than available. Is that normal? |
Which client? |
meh I guess its the replica that is unavailable. That is probably just because I am running stand-alone. |
Yes. It all looks normal to me. And the original error you posted goes away if you wait a bit? |
Seems to have thanks! Next step SSO :) |
@dsyer why this exception is normal? I think there is bug in implementation of private boolean isReplicaAvailable(String myAppName, String url) {
try {
String givenHostName = new URI(url).getHost();
Application app = PeerAwareInstanceRegistry.getInstance()
.getApplication(myAppName, false);
for (InstanceInfo info : app.getInstances()) {
if (info.getHostName().equals(givenHostName)) {
return true;
}
}
givenHostName = new URI(url).getHost();
} catch (Throwable e) {
logger.error("Could not determine if the replica is available ", e);
}
return false;
} since app can be null by contract of |
I guess I agree. But that code is in |
@dsyer, ok |
Its seems that issue has been already fixed in https://github.com/Netflix/eureka/releases/tag/v1.3.0 |
Should be fixed in Spring Cloud Netflix 1.1 then (unless they had a regression). |
So I have this project I am trying to get working in a certain way and I keep running into stuff, so I have started a public repo that I can create a simpler example with, and maybe it will help others to as it evolves.
I was trying to get the standalone eureka server configuration working as outlined in the documentation and I get this exception below when I hit the dashboard. You can reproduce from here:
https://github.com/wgorder/service-discovery
The text was updated successfully, but these errors were encountered: