PH65395: SERVER TERMINATES ABNORMALLY DUE TO A TIMING WINDOW WHEN OOME IS BEING PROCESSED.

APAR status

• Closed as program error.

Error description

• A stop command was issued against WebSphere Application server
  while around the same time, java/lang/OutOfMemoryError was
  issued in a servant region. That resulted in "no new threads"
  status to be not set which lead WebSphere to believe something
  unexpected happened. Instead of normal termination,
  nativeThreadTerm code was called which directed main thread to
  terminate. Subsequently, JVM encountered GPF error - ABEND 0C4.
  
  Controller:
  BBOO0133I WEBSPHERE FOR Z/OS STOP COMMAND ISSUED FOR SERVER
  BBOS001.
  
  Servant:
  JVMDUMP055I Processing dump event "systhrow", detail
  "java/lang/OutOfMemoryError"
  ...
  BBOO0159E Thread Type (5) SRT died.
  BBOO0021E Assertion failed: '0', file ./bbgorobj.cpp, line 167.
  BBOO0035W TERMINATING THE CURRENT PROCESS, REASON=C9C21244.
  BBOO0006E WEBSPHERE FOR Z/OS PROCESS WSD1G36 ENDED ABNORMALLY,
  REASON=C9C2120C.
  ...
  JVMDUMP039I Processing dump event "gpf", detail "" at <date>
  <time> - please wait.
  
  The code will be updated to check a different flag and end
  normally without telling the main thread to abend.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  V8.5 for z/OS                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND0C4/ABENDS0C4 in the JVM because   *
  *                      structures are gone.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  java/lang/OutOfMemoryError caused the servant thread to assert
  and direct the main thread to abend because m_noNewThreads
  was not set. The abend of the main thread leads to a 0C4 abend
  in the JVM because the JVM is referencing structures that are
  gone.
  

Problem conclusion

• Updated the code to check a different flag and not assert
  when the server is stopping.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.28 and 9.0.5.24.
  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 FOR Z

• Fixed component ID

  5655I3500

Applicable component levels