WebGate Communication Failing Due To OAM Server Not Listening On Proxy Port
Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Initial complaint is that the OAM WebGate is unable to contact any access servers. Upon investigation it was determined that the OAM Managed server was starting successfully, but did not listen on the OAM proxy port (5575 by default). Additionally it was noted that the managed server started exceptionally quickly (on the order of 15 to 20 seconds) and there didn't appear to be any oracle.oam modules executed during the startup.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms