From 62521f38e81024683f5a3886ecda4c56de3a1eba Mon Sep 17 00:00:00 2001 From: Niklas Herder Date: Thu, 8 Sep 2016 11:24:11 +0200 Subject: [PATCH] Fix lastFetch status calculation. Was previously milliseconds/seconds when calculating whether to display the message about reporting failures. --- .../cloud/netflix/eureka/EurekaHealthIndicator.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-cloud-netflix-eureka-client/src/main/java/org/springframework/cloud/netflix/eureka/EurekaHealthIndicator.java b/spring-cloud-netflix-eureka-client/src/main/java/org/springframework/cloud/netflix/eureka/EurekaHealthIndicator.java index 975cc820..d7dc499a 100644 --- a/spring-cloud-netflix-eureka-client/src/main/java/org/springframework/cloud/netflix/eureka/EurekaHealthIndicator.java +++ b/spring-cloud-netflix-eureka-client/src/main/java/org/springframework/cloud/netflix/eureka/EurekaHealthIndicator.java @@ -77,7 +77,7 @@ public class EurekaHealthIndicator implements DiscoveryHealthIndicator { status = new Status("UP", "Eureka discovery client has not yet successfully connected to a Eureka server"); } - else if (lastFetch > clientConfig.getRegistryFetchIntervalSeconds() * 2) { + else if (lastFetch > clientConfig.getRegistryFetchIntervalSeconds() * 2000) { status = new Status("UP", "Eureka discovery client is reporting failures to connect to a Eureka server"); builder.withDetail("renewalPeriod",