PM78950: An XS catalog server throws java.Io.IOException in remote JMX listener during startup, while continuing to process requests.

APAR status

• Closed as program error.

Error description

• The exception is displayed in a First Failure Data Capture
  (FFDC) file.  The details of the exception are:
  Exception:java.io.IOException SourceId:com.ibm.ws.objectgrid.
  management.RemoteJMXListener.getJMXConnector ProbeId:220
  Reporter:com.ibm.ws.objectgrid.management.RemoteJMXListener@29f6
  03c0 java.io.IOException: Failed to retrieve RMIServer stub:
  javax.naming.NameNotFoundException: Context: , name:
  JMXConnector: First component in name JMXConnector not found.
  [Root exception is
  org.omg.CosNaming.NamingContextPackage.NotFound:
  IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
  
  The XS console message center will not display subsequent
  message notifications from other servers when this occurs.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere eXtreme Scale catalog servers     *
  *                  embedded in WebSphere Application Server    *
  *                  Version 8.5 that have the default enabled   *
  *                  Management Concentrator, using the XIO      *
  *                  protocol.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: The WebSphere eXtreme Scale catalog     *
  *                      server log and the Message Center       *
  *                      contains FFDC record messages that      *
  *                      read: "java.io.IOException: Failed to   *
  *                      retrieve RMIServer stub:                *
  *                      javax.naming.NameNotFoundException".    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The WebSphere eXtreme Scale catalog server log and the Message
  Center contain FFDC record messages generated during the
  initialisation of the catalog and container servers in the
  process of registering Java Management Extensions (JMX)
  notification subscribers. The error message is associated with
  a failure to connect to a newly discovered but not completely
  initialised container servers.
  

Problem conclusion

• The fix is included in the 8.6.0.1 fixpack.
  

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