Coherence node got restarted in the SSL configured cluster due to security scanner or non-ssl client
(Doc ID 2137471.1)
Last updated on SEPTEMBER 15, 2022
Applies to:Oracle Coherence - Version 220.127.116.11 and later
Information in this document applies to any platform.
Coherence nodes in the cluster get terminated during security scans. Suppose the machine hosting the coherence proxy node of the coherence cluster is in the DMZ zone and its firewall security scanner is on and is scheduled to run at times, the security scanner is causing the proxy node go down. It is expected that coherence runtime should handle the security scanner messages intelligently and process should not be terminated.
Security (firewall) scanners are possible to cause this problem. This happens when a client try to connect to the SSL configured coherence cluster, this would be usually the case when non-SSL clients or scanners trying to connect to the SSL configured cluster.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document