My Oracle Support Banner

Oracle Access Manager (OAM) 12.2.1.4 - Second OAM Managed Server Stops Listening On The Proxy Port After wm/OAPOverRestWM Tuning (Doc ID 3002101.1)

Last updated on FEBRUARY 02, 2024

Applies to:

Oracle Access Manager - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

1. Tune Capacity and MaxThreadsCount for wm/OAPOverRestWM as documented.

2. Restart the whole OAM domain.

3. The second OAM managed server (running on a different machine/host/node) does not listen on the proxy port, default 5575. All webgates throw connection errors to that server and any telnet command sent to the proxy port fails.

Changes

 wm/OAPOverRestWM was tuned.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.