You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When having custom health check written in Java e.g. com.test.HealthCheck, which fails, then expected behavior when asking for readiness would to see following log:
Not Healthy: Check [com.test.HealthCheck] not ok
Actual Behavior
Currently, log is:
Check [akka.management.internal.HealthChecksImpl$$Lambda$1599/0x0000000100e84040] not ok
Using Scala Function0<Future<Boolean>> instead of Supplier can be used as workaround.
Internally it looks that Java Supplier is converted and then the name of the original class is gone.
The text was updated successfully, but these errors were encountered:
Versions used
Akka version: 2.6.13
Akka-management: 1.0.9
Expected Behavior
When having custom health check written in Java e.g.
com.test.HealthCheck
, which fails, then expected behavior when asking for readiness would to see following log:Actual Behavior
Currently, log is:
Using Scala
Function0<Future<Boolean>>
instead ofSupplier
can be used as workaround.Internally it looks that Java
Supplier
is converted and then the name of the original class is gone.The text was updated successfully, but these errors were encountered: