Coherence node got restarted in the SSL configured cluster due to security scanner or non-ssl client
Last updated on MAY 26, 2016
Applies to:Oracle Coherence - Version 126.96.36.199 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms