My Oracle Support Banner

10.1.3.X AS Control Fails To Access OC4J Administration Pages With The Error "A connection could not established to some members of the group" (Doc ID 852731.1)

Last updated on MARCH 20, 2020

Applies to:

Enterprise Manager for Fusion Middleware - Version 10.1.3.3.0 to 10.1.3.5.0
Information in this document applies to any platform.

Symptoms

When using AS Control in Oracle AS 10.1.3 to administer a group of OC4J instances for configuration
purposes the following error is shown in the browser:

"A connection could not established to some members of the group <groupname>.

Common causes for this failure are an authentication error or a JMX proto mismatch."



At the same time the $ORACLE_HOME/j2ee/home/log/ascontrol.log file contains the following error messages:

2008-11-28 09:18:25,961 [EMUI_09_18_24_/console/ias/cluster/topology] WARN
javasso.JMXJavaSSOConfAdminBean isJssoConfigured.1067 - --------
Exception in checking jsso for server
ias:j2eeType=J2EEServer,name=<OC4JINSTANCENAME>,J2EEServerGroup=<GROUPNAME>,ASInstance=&
lt;ASINSTANCENAME>


javax.management.RuntimeMBeanException: RuntimeException thrown by the invoke method of the
Dynamic MBean
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:227)...
Caused by: javax.management.RuntimeMBeanException:
Error while getting JMX Connector
for:opmnId:<host>:<port>,hostName:<host>,iasInstanceName:<iasinstanceName>,c
omponentName:<groupname>,processTypeName:<OC4JPROCESS>,
processSetName:<groupname>,type:OC4J,pid:xxxx,uid:YYYYY,
index:1,startTime:1227858687547,upTime:1612399,cpuTime:98001,memoryUsed:92560,
privateMemory:42056,sharedMemory:50504,heapSize:57144

... 52 more


Additionally, after enabling TRACE:32 level in oracle.security.jazn loggers and oracle.j2ee.security as follows:

a) Edit $ORACLE_HOME/j2ee/home/config/j2ee-logging.xml file
b) Add the new <logger section within the <loggers> tags, as follows:


<loggers>
...
  <logger name='oracle.security.jazn' level='TRACE:32' useParentHandlers='false'>
   <handler name='oc4j-handler'/>
  </logger>
  <logger name='oracle.j2ee.security' level='TRACE:32' useParentHandlers='false'>
   <handler name='oc4j-handler'/>
  </logger>

...
</loggers>



Lter on the $ORACLE_HOME/j2ee/<oc4j instance>/log/<group name>/oc4j/log.xml file for the managed OC4J instance contains messages as follows:

<MSG_TEXT>Authenticating cred=*******  _format=1</MSG_TEXT>
<MSG_TEXT>AUTH FAILURE: obsPD[24] != _cred[24]</MSG_TEXT>
<<--------------------!!!!!
<MSG_TEXT>        [RealmLoginModule] authentication failed</MSG_TEXT>
<MSG_TEXT>        [AbstractLoginModule] aborted authentication
attempt.</MSG_TEXT>
   <SUPPL_DETAIL><![CDATA[javax.security.auth.login.FailedLoginException
    at
oracle.security.jazn.login.module.RealmLoginModule.authenticate(RealmLoginModule.java:131)
    at
oracle.security.jazn.login.module.RealmLoginModule.authenticate(RealmLoginModule.java:86)
    at
oracle.security.jazn.login.module.AbstractLoginModule.login(AbstractLoginModule.java:265)
    at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
    at
javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
    at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
    at java.security.AccessController.doPrivileged(Native Method)

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

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