While Trying To Administer Secured OC4J From Oracle Application Server Console (EM), It Is Failing With Error "Unable to make a connection to OC4J instance ..."
(Doc ID 862446.1)
Last updated on FEBRUARY 13, 2024
Applies to:
Enterprise Manager for Fusion Middleware - Version 10.1.3.1.0 to 10.1.3.5.0Oracle Containers for J2EE - Version 10.1.3.1.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.
Symptoms
After securing an OC4J instance using Oracle Application Server Web Services Security Guide documentation, here, the Oracle Application Server Console (AS Console) is experiencing the following symptoms:
- The initial page, Cluster-Topology is available after initial log in.
- When trying to administer an OC4J-instance without the options "Djavax.net.ssl.keyStore" and "Djavax.net.ssl.trustStore", it works fine.
- When trying to administer an OC4J_Instance that has these parameters included in opmn.xml, clicking on administration link in AS Console, it fails with the following error message:
After removing the SSL parameters from java options in opmn.xml file and restarting the container, administration is possible again.
Changes
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 |