CAS 6.1.3 Discovery Client not initialized

[Maksim Kopeyka]

Hi Guys,

The cas/actuator/health endpoint returns json with "Discovery Client not initialized" status after updating from CAS 6.0.3 to 6.1.3 . Does it mean I should use additional properties to fix it or it's related to network configuration?

{
   "description":"Discovery Client not initialized",
   "status":"UNKNOWN",
   "components":{
      "discoveryComposite":{
         "description":"Discovery Client not initialized",
         "status":"UNKNOWN",
         "components":{
            "discoveryClient":{
               "description":"Discovery Client not initialized",
               "status":"UNKNOWN"
            }
         }
      },
      "diskSpace":{
         "status":"UP",
         "details":{
            "total":19163136000,
            "free":9581965312,
            "threshold":10485760
         }
      },
      "memory":{
         "status":"UP",
         "details":{
            "freeMemory":387328608,
            "totalMemory":518979584
         }
      },
      "ping":{
         "status":"UP"
      },
      "refreshScope":{
         "status":"UP"
      },
      "session":{
         "status":"UP",
         "details":{
            "name":"TicketRegistryHealthIndicator",
            "sessionCount":0,
            "ticketCount":0,
            "message":"OK"
         }
      },
      "system":{
         "status":"UP",
         "details":{
            "systemUsage":0.019733628072337486,
            "systemLoad":0.22,
            "processUsage":5.457595723356569E-4,
            "jvmUsed":2.41595672E8,
            "jvmCommitted":6.35633664E8,
            "heapUsed":1.32786576E8,
            "heapCommitted":5.18979584E8,
            "uptime":239.72,
            "requests":0.0,
            "maxRequest":0.0
         }
      }
   }
}

[Maksim Kopeyka]

Still have this problem even on my local PC. It worked fine with 6.0.3 but doesn't work with 6.1.3. Looks like a bug...

[Dmitriy Kopyleenko]

Looks like something that is coming from Spring Boot 2.2: https://github.com/spring-cloud/spring-cloud-commons/issues/633

D.

On February 25, 2020 at 05:32:53, 'Maksim Kopeyka' via CAS Community (cas-...@apereo.org) wrote:

Still have this problem even on my local PC. It worked fine with 6.0.3 but doesn't work with 6.1.3. Looks like a bug...

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/8f128a52-3f06-4091-8fc0-8da6de4b3f00%40apereo.org.

[Maksim Kopeyka]

Dmitriy,

Good point, thank you.

I solved my issue via adding this property

spring.cloud.discovery.client.composite-indicator.enabled=false

On Tuesday, February 25, 2020 at 3:12:40 PM UTC+2, Dmitriy Kopyleenko wrote:

Looks like something that is coming from Spring Boot 2.2: https://github.com/spring-cloud/spring-cloud-commons/issues/633

D.

On February 25, 2020 at 05:32:53, 'Maksim Kopeyka' via CAS Community (cas-...@apereo.org) wrote:

Still have this problem even on my local PC. It worked fine with 6.0.3 but doesn't work with 6.1.3. Looks like a bug...

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cas-...@apereo.org.