PM92694: The xscmd command returns an error indicating that the server closed the client connection.

APAR status

• Closed as program error.

Error description

• The following error occurs when xscmd is called:
  
  java.util.NoSuchElementException at
  java.util.HashMap$AbstractMapIterator.makeNext(HashMap.java:200)
  at java.util.HashMap$KeyIterator.next(HashMap.java:271)
  at
  com.ibm.ws.xs.admin.util.WXSJMXQueryThread.run(WXSJMXQueryThread
  .java:132)
  at
  java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoo
  lExecutor.java:897)
  at
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE
  xecutor.java:919)
  at java.lang.Thread.run(Thread.java:738)
  
  An error is seen in the logs:
  misc WServerCommunicatorAdmin reqIncoming The server has decided
  to close this client connection.
  

Local fix

• No workaround.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere eXtreme Scale users who invoke    *
  *                  the                                         *
  *                  xscmd command.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When running the xscmd command, an      *
  *                      error occurs and the server closes      *
  *                      the client connection.                  *
  ****************************************************************
  * RECOMMENDATION:  Managed Beans (MBeans) are enabled by       *
  *                  default. However, if you have explicitly    *
  *                  disabled them, the xscmd command does not   *
  *                  connect to the eXtreme Scale catalog or     *
  *                  container servers.  Be sure to enable       *
  *                  MBeans.                                     *
  ****************************************************************
  MBeans might not have been correctly registered to the MBean
  server, even if MBeans are enabled. This is based on the order
  that beans are first registered with the server during startup.
  If the MBean is not an IBM class, xscmd will not be able to
  retrieve information from the MBean.
  

Problem conclusion

• This APAR fix registers to the correct IBM MBean to allow the
  xscmd command to access information from the eXtreme Scale
  catalog and container servers.
  

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

• R711 PSY

     UP

• R850 PSY

     UP

• R860 PSY

     UP