Oracle Access Manager (OAM) Common Cause for "Oracle Access Manager Operation Error" "OAM-04020" (Doc ID 2351492.1)

There are times when the Oracle Access Manager (OAM) Managed Server Oracle Access Protocol (OAP) communication (default port ) with the WebGate can hang, resulting in the end user having issues when trying to authenticate to protected resources. A common reason for this is due to the growing connections over a period of time until the adverse effect is seen; which when this occurs the only solution is to restart the Access server in question. this can be due to network or load issue that require tuning

At the highest level there is a communications issue between the OAM WebGate and the OAM server on the OAP channel/port. Everything works until a point is reached were the configuration limits are exceeded and requires a restart to reset these parameters/connections.

There are times when the OAM Server OAP communication (port) with the WebGate can hang, resulting in the end user having issues when trying to authenticate to protected resources. A Common reasons for this is due to the growing connections over a period of time until the adverse effect is seen; which when this occurs the only solution is to restart the Access server in question.

There are certain circumstances that can occur that cause the various pieces of the OAM Server and its dynamics of handling connections to build up over time due to its design as a passive listener for client messages. A given thread does -not- periodically wake up  and check for any new data on the socket.  Instead a trigger is set to notify the OAM server if a message arrives and the thread just sleeps indefinitely until this happens. If a third party breaks the connection without notifying the OAM components, no further messages are possible, the thread will never wake.

The issue is typically seen/caused due to tuning issues. Tuning - Network conductivity in regards to the communications between the OAM WebGate and the OAM server on the OAP channel/port.

Everything works until a point is reached were the configuration limits are exceeded and requires a restart to reset these parameters.

Common Symptoms

• Determined one of the WebGates was creating more than 2500 OAP connections on OAM
• Once they disabled the WebGate, they no longer observed any issues
• Tuned the number of WebGate connections and no longer saw the issue