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 MARCH 08, 2017

Applies to:

Enterprise Manager for Fusion Middleware - Version to
Oracle Containers for J2EE - Version to [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 16-Jul-2016***


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:

Unable to make a connection to OC4J instance OC4J_instance_name on Application Server <application_server_instance_name>. A common cause for this failure is an authentication error. The administrator password for each OC4J instance in the Cluster must be the same as the administrator password for the OC4J instance on which Application Server Control is running.

After removing the SSL parameters from java options in opmn.xml file and restarting the container, administration is possible again.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms