PI11520: Unable to get server mbean exception when starting a server registered with an administrative agent.

APAR status

• Closed as program error.

Error description

• Unable to get Server MBean exception when starting a server
  registered with an administrative agent.
  
  getCatalogServicesWCCM Exception during initialization :
  com.ibm.websphere.management.exception.ConnectorException:
  Unable to get Server MBean
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere eXtreme Scale with       *
  *                  WebSphere Application Server                *
  *                  administrative agents.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The WebSphere eXtreme Scale code now    *
  *                      uses the WebSphere Application Server   *
  *                      runtime configuration service to        *
  *                      retrieve it's configuration data        *
  *                      instead of the admin code. This         *
  *                      removes the dependency on the server    *
  *                      MBean being registered.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Users receive a ConnectorException when starting a WebSphere
  eXtreme Scale augmented WebSphere Application Server server
  that is registered with an administrative agent:
  [14. 1. 6   20:37:21:985 KST] 00000001 ConfigUtility E
  getCatalogServicesWCCM Exception during initialization :
  com.ibm.websphere.management.exception.ConnectorException:
  Unable to get  Server MBean
  at
  com.ibm.ws.management.cmdframework.impl.AgentProxyAdminClient.ge
  tServerMBean(AgentProxyAdminClient.java:84)
  at
  com.ibm.ws.management.cmdframework.impl.CommandUtility.getRemote
  CmdMgrMbean(CommandUtility.java:72)
  at
  com.ibm.ws.management.cmdframework.impl.ClientCommandMgr.initCom
  mandMetadata(ClientCommandMgr.java:317)
  at
  com.ibm.ws.management.cmdframework.impl.ClientCommandMgr.createC
  ommand(ClientCommandMgr.java:295)
  at
  com.ibm.ws.objectgrid.integration.ConfigUtility.getCatalogServic
  esWCCM(ConfigUtility.java:174)
  at
  com.ibm.ws.objectgrid.integration.ObjectGridCatalogComponentImpl
  .initialize(ObjectGridCatalogComponentImpl.java:276)
  at
  com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(Con
  tainerHelper.java:1192)
  at
  com.ibm.ws.runtime.component.ContainerHelper.initializeComponent
  (ContainerHelper.java:1099)
  at
  com.ibm.ws.runtime.component.ContainerHelper.initializeComponent
  s(ContainerHelper.java:901)
  at
  com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(
  ContainerImpl.java:776)
  at
  com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(
  ContainerImpl.java:750)
  at
  com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.ja
  va:353)
  at
  com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl
  .java:292)
  at
  com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:223)
  at
  com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:686)
  at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
  Method)
  at
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
  Impl.java:60)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java:37)
  at java.lang.reflect.Method.invoke(Method.java:611)
  at
  com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:23
  4)
  at
  com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96)
  at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
  Method)
  at
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
  Impl.java:60)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java:37)
  at java.lang.reflect.Method.invoke(Method.java:611)
  at
  org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodW
  ithException(EclipseAppContainer.java:587)
  at
  org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseApp
  Handle.java:198)
  at
  org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.run
  Application(EclipseAppLauncher.java:110)
  at
  org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.sta
  rt(EclipseAppLauncher.java:79)
  at
  org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart
  er.java:369)
  at
  org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart
  er.java:179)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
  Method)
  at
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
  Impl.java:60)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java:37)
  at java.lang.reflect.Method.invoke(Method.java:611)
  at
  org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
  at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
  at org.eclipse.core.launcher.Main.run(Main.java:981)
  at
  com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLaunche
  r.java:380
  The WebSphere Application Server admin code behaves
  differently when run an an application server that is
  registered with an administrative agent. Instead of using the
  server's MBean object directly, the admin code tries to use
  the MBean. Since the Server MBean has not been registered,
  this call fails with the exception.
  

Problem conclusion

• Install the provided iFix.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R860 PSY

     UP