PI28764: WEBSPHERE CONTROL REGION HUNG AFTER JVM ERROR

Fixes are available

APAR status

Closed as program error.

Error description

When JVM takes an gpf error during an storage allocation that
causes a 0C4 storage exception. 04C abend caused websphere to
hang and failed to take down the control region.  Review the
0C4 dump shows :
    1        j9heap_allocate                       Except
    2        allocate_memory32                Call
    3        j9mem_allocate_memory32   Call
    4        allocateJavaStack                   Call
    5        internalGrowJavaStack           Call
    6        growJavaStack                        Call
    7        RUNJAVATHREAD                  Call
    8        javaProtectedThreadProc       Call
    9        j9sig_protect                           Call
    10       javaThreadProc

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V8.0 and V8.5                        *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application server for z/OS   *
*                      Controller is hung after a call to our  *
*                      JVM Abort routine.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Subsequent failures in the JVM caused the JVM to drive our
JVM Abort routine (resides in bbolsys.cpp).  The JVM Abort
routine drove our native ServerManagement::cancel() routine.
The cancel() routine set our m_cancel flag and drove our
BOA deactivate_impl routine.  Our deactivate_impl routine is
called for both "NORMAL" and "ABNORMAL" termination requests.
The deactivate_impl invoked a Java notification service to
inform components of a server stop event.  This upcall from
native to Java hung in the JVM and caused the termination
process to hang.   The target Java notification service should
only be invoked for "NORMAL" termination requests.
The JVM notification can be observed on the call stack along
with deactivate_impl at the time of the hang.  The notification
routine name is doNotifyServerStopping.  Also, message
BBOO0158E is issued on entry to the native JVM Abort routine
in bbolsys.cpp.

Problem conclusion

Code has been modified within the deactivate_impl routine to
not drive the JVM notification service on "ABNORMAL"
termination requests.

APAR PI28764 is currently targeted for inclusion in Ficks
Packs 8.0.0.10 and 8.5.5.5 of WebSphere Application Server.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

In addition, please refer to URL:
http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack PTF information.

Temporary fix

Comments

APAR Information

APAR number
PI28764
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-10-30
Closed date
2014-11-05
Last modified date
2014-11-05

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

R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI28764: WEBSPHERE CONTROL REGION HUNG AFTER JVM ERROR

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R850 PSY

Document Information

Share your feedback

Need support?