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
I've found that the WARN log message is "Cannot refresh Redis Cluster topology", after AWS Elasticache instance reboot.
Although the log was printed every topology refresh period, all requests was fine.NO connection issue though.it just print warning logs.
Unable to connect to [xxxxxxx:port]: PKIX path validation failed: java.security.cert.CertPathValidatorException: Unable to determine revocation status due to network error
Stack trace
i.l.c.c.t.DefaultClusterTopologyRefresh$CannotRetrieveClusterPartitions: Cannotretrieveclusterpartitionsfrom [rediss://********************@xxxxxx:port]Details:
[rediss://********************@xxxxx:port]: PKIX path validation failed: java.security.cert.CertPathValidatorException: Unable to determine revocation status due to network errorSuppressed: java.io.EOFException: notenoughcontentatsun.security.util.DerValue.<init>(DerValue.java:425)
atsun.security.util.DerValue.<init>(DerValue.java:340)
ats.s.provider.certpath.OCSPResponse.<init>(OCSPResponse.java:200)
atsun.security.provider.certpath.OCSP.check(OCSP.java:196)
ats.s.provider.certpath.RevocationChecker.checkOCSP(RevocationChecker.java:785)
ats.s.provider.certpath.RevocationChecker.check(RevocationChecker.java:369)
How do you verify that "all requests are fine. NO connection issue though."?
From the code I see in Lettuce the WARN message you are seeing is indicating that the topology refresh has failed.
The indicated issue is that the revocation status of the certificate could not be established due to network error.
Have in mind that a topology refresh failing would not stop the driver from operating and using the topology it already has from previous attempts, but the topology information would not be updated until the network issue is resolved.
Bug Report
Current Behavior
I've found that the WARN log message is "Cannot refresh Redis Cluster topology", after AWS Elasticache instance reboot.
Although the log was printed every topology refresh period, all requests was fine.NO connection issue though.it just print warning logs.
Unable to connect to [xxxxxxx:port]: PKIX path validation failed: java.security.cert.CertPathValidatorException: Unable to determine revocation status due to network error
Stack trace
Input Code
Input Code
Expected behavior/code
"Cannot refresh Redis Cluster topology" log should no longer be printed.
Environment
Possible Solution
Additional context
The text was updated successfully, but these errors were encountered: