PM77893: Orphan threads are not cleaned up after stopping the server with the ServerFactory.stopServer() method.

APAR status

• Closed as program error.

Error description

• Threads are orphaned when the ServerFactory.getInstance() method
  returns a failure or when the ServerFactory.stopServer()
  method is called.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All WebSphere eXtreme Scale users who       *
  *                  call ServerFactory.getInstance() or         *
  *                  ServerFactory.stopServer()                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: A thread is orphaned when a             *
  *                      ServerFactory.getInstance()             *
  *                      method returns a failure or when        *
  *                      ServerFactory.stopServer() is called.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A thread was prematurely started during server startup and the
  thread was not cleaned up when a failure occurred. Also,
  threads were not stopped when the server was being torn down.
  

Problem conclusion

• The problematic thread was altered to only start when it is
  needed, instead of during startup. This will prevent the
  condition where the thread is orphaned during a failed startup.
  The ServerFactory.stopServer() method will now also stop the
  thread when called.
  

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