PH32612: UNEXPECTED SERVER SHUTDOWN PRODUCES NO ADDITIONAL DEBUG DATA

APAR status

• Closed as program error.

Error description

• When the WebSphere Application Server JVM is stopped through
  some means other than the typical supported stop operation, such
  as a System.exit() call or an external signal, it can be
  difficult to determine the source of that call. Diagnostics
  exist for this type of issue, but they require enablement in
  advance through the use of JVM system properties.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: An unexpected shutdown of the server    *
  *                      process provides no diagnostic data     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WAS provides a system property (-
  Dcom.ibm.ws.runtime.dumpShutdown)
  that creates additional data on server shutdown, for debugging
  unexpected stop events - stack traces for the stop() method and
  JVM shutdown hook, and a javacore or thread dump to capture the
  wider state of the Java process. Because it's enabled through a
  system property, this diagnostic output must be explicitly
  enabled
  before a server is launched, and it's often impossible to
  anticipate (or recreate) an unexpected server shutdown event.
  

Problem conclusion

• Logic was added to create the equivalent of dumpShutdown output
  anytime the server is stopped without calling the Server Mbean's
  stop() method (which is invoked by node agent stop requests and
  the stopServer.sh/bat script). Note that this function requires
  that the JVM continue to operate after the shutdown begins, so
  it will not be executed in the event of an immediate process
  termination, such as from Runtime.halt() or kill -9.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.19 and 9.0.5.7. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP