Oracle Access Manager (OAM) Agent For JBoss Failed To Connect To OAM Server After Upgrade From 11gR2PS2BP04 To 11gR2PS3
(Doc ID 2080171.1)
Last updated on JUNE 09, 2017
Applies to:Oracle Access Manager - Version 126.96.36.199.4 and later
Information in this document applies to any platform.
JBoss (EAP) 5.1.2.
Oracle Access Manager (OAM) Agent for JBoss failed to connect to OAM server after upgrade from 11gR2PS2BP04 to 11gR2PS3.
OAM Agent is installed in JBoss (EAP) 5.1.2.
ASDK used is oamasdk-api-188.8.131.52.0.jar.
This configuration works fine with OAM 11gR2PS2, but failed after upgrade to PS3. OAM is up and running at the time the error is raised in JBoss logs, which show the following error:
2015-10-30 15:45:06,703 SEVERE [AccessLogger] (main) Internal error.
java.lang.Exception: Failed to communicate with any of configured Access Server, ensure that it is up and running.
2015-10-30 15:45:06,704 SEVERE [AccessLogger] (main) An AccessGate with id hostname.domain has not been configured through the Access System Console.
2015-10-30 15:45:06,710 SEVERE [AccessLogger] (main) Oracle Access SDK initialization failed.
oracle.security.am.asdk.AccessException: OAMAGENT-02055: An AccessGate with id hostname.domain has not been configured through the Access System Console.
Upgraded from JDK 1.7.0_55 to JDK 1.7.0_85
Upgraded from 11gR2PS2BP04 to 11gR2PS3
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