PM43077: ABEND S0C4 RC=38 IN THE CONTROL REGION PRECEEDED BY NULLPOINTEREXCEPTION

Fixes are available

APAR status

Closed as program error.

Error description

Control region can terminate with an ABEND S0C4 RC=38 due to a
defect in the error handling code  triggered by
NullPointerException.

The TCB with an 0C4 completion code has the following native
traceback:

acrwObj::postIfSynchronous()          +00000040  *PATHNAM
ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)
ACR_ExecutionRoutine

The 0C4 was caused do to a defect in the error handling path
triggered by NullPointerException issued in XMemChannel code:

com.ibm.ws.proxy.channel.http.HttpProxyServiceContextImpl.localP
roviderPreparation(HttpProxyServiceContextImpl.java:4118)
 at com.ibm.ws.proxy.channel.http.HttpProxyConnectionLink.proces
sResponseWork(HttpProxyConnectionLink.java:1414)
 at com.ibm.ws.proxy.channel.http.HttpProxyConnectionLink.transf
erProcessingToResponsePath(HttpProxyConnectionLink.java:1864)
 at com.ibm.ws.proxy.channel.http.HttpInboundReadBodyCallback.er
ror(HttpInboundReadBodyCallback.java:98)
 at com.ibm.ws.http.channel.inbound.impl.HttpISCBodyReadCallback
.error(HttpISCBodyReadCallback.java:95)
....
at com.ibm.ws.proxy.channel.http.HttpProxyConnectionLink.proces
sRequestWork(HttpProxyConnectionLink.java:1016)
 at com.ibm.ws.proxy.channel.http.HttpInboundReadBodyCallback.co
mplete(HttpInboundReadBodyCallback.java:68)

Note, this apar is going to prevent the abend of the controller.
It does not fix the NPE.

Another occurrence of this problem was triggered by a different
path into the catch block with this exception. Again causing the
code to result in the abend 0C4.

java.io.IOException: Error occurred during communications
 processing. EDC8121I Connection reset.
 at com.ibm.ws.tcp.channel.impl.ZAioTCPChannelCPPUtilities.read(
Native Method)
 at com.ibm.ws.tcp.channel.impl.ZAioTCPReadRequestContextImpl.re
adCommon(ZAioTCPReadRequestContextImpl.java:613)
 at com.ibm.ws.tcp.channel.impl.ZAioTCPReadRequestContextImpl.re
ad(ZAioTCPReadRequestContextImpl.java:154)
 at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.fillABuf
fer(HttpServiceContextImpl.java:4140)
 at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readSing
leBlock(HttpServiceContextImpl.java:3372)
 at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readBody
Buffer(HttpServiceContextImpl.java:3478)
 at com.ibm.ws.http.channel.inbound.impl.HttpInboundServiceConte
xtImpl.getRequestBodyBuffer(HttpInboundServiceContextImpl.java:1
704)
 at com.ibm.ws.soapchannel.monitor.impl.SOAPHttpInboundServiceCo
ntext._getRequestBodyBuffer(SOAPHttpInboundServiceContext.java:2
53)
 at com.ibm.ws.soapchannel.monitor.impl.SOAPHttpInboundServiceCo
ntext.getRequestBodyBuffer(SOAPHttpInboundServiceContext.java:31
5)
 at com.ibm.ws.proxy.channel.http.HttpProxyServiceContextImpl.se
ndPartialRequestBody(HttpProxyServiceContextImpl.java:2660)
 at com.ibm.ws.proxy.channel.http.HttpProxyConnectionLink.proces
sRequestWork(HttpProxyConnectionLink.java:1011)
 at com.ibm.ws.proxy.channel.http.HttpOutboundWriteBodyCallback.
complete(HttpOutboundWriteBodyCallback.java:59)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 and V8.0.                       *
****************************************************************
* PROBLEM DESCRIPTION: A WebSphere Application Server for      *
*                      z/OS Controller terminates with an      *
*                      ABEND0C4/ABENDS0C4 while receiving a    *
*                      large HTTP request.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The TCB that encountered the ABEND0C4 will have the following
native traceback:
1  acrwObj::postIfSynchronous()
2  ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)
3  ACR_ExecutionRoutine
In addition, it is likely that an FFDC record will have been
printed just prior to the abend with the following stack
elements at the bottom of the traceback:
at com.ibm.ws390.channel.xmem.XMemWriteRequestContext.
getChunk(XMemWriteRequestContext.java:814)
at com.ibm.ws390.channel.xmem.XMemConnLink.
getNextChunk(XMemConnLink.java:1183)
at com.ibm.ws390.xmem.XMemCRBridgeImpl.
getNextChunk(XMemCRBridgeImpl.java:458)
at com.ibm.ws390.xmem.XMemCRCppUtilities.
getNextChunk(XMemCRCppUtilities.java:146)
The actual exception being caught does not matter.  The problem
is triggered when any unexpected exception gets thrown to the
stack elements shown above.  The exception handling path in the
above stack elements inadvertently deletes native storage that
had already been deleted.

Problem conclusion

Code has been fixed to avoid double-deleting the native storage
in question.

APAR PM43077 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.21 of WebSphere Application Server V7.0
and Fix Pack 8.0.0.2 of WebSphere Application Server V8.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM43077
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-05
Closed date
2011-07-25
Last modified date
2012-02-03

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

R700 PSY UK74996
UP12/01/18 P 1201

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM43077: ABEND S0C4 RC=38 IN THE CONTROL REGION PRECEEDED BY NULLPOINTEREXCEPTION

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

R700 PSY UK74996

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?