CoreRemoteMBeanServer.fetchMBeanServerEjbRemote Error On Creating a 10.1.3.1 OC4J Instance (Doc ID 403622.1)

Last updated on MARCH 28, 2024

Applies to:

Symptoms

When creating an OC4J instance from the command line using:
$ORACLE_HOME/bin/createinstance -instanceName [name]
a prompt is issued to supply the oc4jadmin password.

If the supplied oc4jadmin passsword does not match the one supplied at AS Instance install time, the following exception occurs:

SEVERE: CoreRemoteMBeanServer.fetchMBeanServerEjbRemote Error reading application-client
descriptor: Error communicating with server: Lookup error: javax.naming.AuthenticationException:
Not authorized; nested exception is:
javax.naming.AuthenticationException: Not authorized; nested exception is:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not
authorized; nested exception is:
javax.naming.AuthenticationException: Not authorized [Root exception is
javax.naming.AuthenticationException: Not authorized] for URL:
ormis://[server]:12702/defaultjavax.naming.NamingException: Error reading application-client
descriptor: Error communicating with server: Lookup error: javax.naming.AuthenticationException:
Not authorized; nested exception is:
:
Caused by: javax.naming.AuthenticationException: Not authorized
at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:99)
at
oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:646)
at
com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:190)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:174)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
:

Moreover, the OC4J instance is created but it is not possible to start and stop it, either from the command line or from AS Control.

Any subsequent attempt to edit or delete the newly-created OC4J instance from AS Control results in the following error message:
Error
Unable to make a connection to OC4J instance [OC4J instance name] on Application Server [AS 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.

It is possible to remove the OC4J instance using:
$ORACLE_HOME/bin/removeinstance -instanceName [oc4j instance name]

although the same exception will be generated as when the OC4J instance was created.
 

Cause

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