OAM 11g Failed To Communicate With Webgates After OAM Server Running For Some Time
(Doc ID 1987189.1)
Last updated on AUGUST 09, 2018
Applies to:Oracle Access Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
One of two clustered OAM Servers stopped responding and failed to communicate with WebGates.
WebGates give errors "The AccessGate is unable to contact any Access Servers." or similar connection related errors.
In the Weblogic admin console, the status of the servers was showing up. However OAM diagnostics page showed that the server was down.
Restart of the managed server resolved the issue temporarily.
The OAM diagnostic logs showed "Too many open files" errors.
All bad socket connections correspond to the OAM managed server PID. The number keeps increasing.
This is noticed in very high numbers only on one OAM server in the cluster. On other server it is very low and does not increase.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|