PM05685: HTTP RESPONSE NOT FLUSHED ON Z/OS AND THE HTTP PROXY HAS STOPPED READ ON THES CONNECTION

Fixes are available

APAR status

Closed as program error.

Error description

The customer received the following error in the
WebSphere log on z/OS stating the thread was
hung.
.
In the Servant Regionjob log, there is the following:
.
Trace: 2010/01/13 08:50:37.873 01 t=9C7938
  ThreadId: 000008cd
  FunctionName: com.ibm.ws.runtime.component.
                ThreadMonitorImpl
  SourceId: com.ibm.ws.runtime.component.
            ThreadMonitorImpl
  Category: WARNING
  ExtendedMessage: BBOO0221W: WSVR0605W: Thread
"WebSphere:ORB.thread.pool t=009bae88" (00000034) has
been active for 739867 milliseconds and may be hung.
There is/are 1 thread(s) in total in the server
that may be hung.
.at com.ibm.ws390.xmem.XMemSRCppUtilities.
        doPushService(Native Method)
.at com.ibm.ws390.channel.xmem.XMemReadRequestContext.
        read(XMemReadRequestContext.java:227)
.at com.ibm.ws.http.channel.impl.
        HttpServiceContextImpl.fillABuffer
        (HttpServiceContextImpl.java:4134)
.at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.
        readSingleBlock(HttpServiceContextImpl.java:3366)
.at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.
        readBodyBuffer(HttpServiceContextImpl.java:3472)
.at com.ibm.ws.http.channel.inbound.impl.
        HttpInboundServiceContextImpl.
        getRequestBodyBuffer
        (HttpInboundServiceContextImpl.java:1704)
.at com.ibm.ws.webcontainer.channel.
        WCCByteBufferInputStream.bufferIsGood
        (WCCByteBufferInputStream.java:121)
.at com.ibm.ws.webcontainer.channel.
        WCCByteBufferInputStream.read
        (WCCByteBufferInputStream.java:87)
.at com.ibm.ws.webcontainer.srt.http.
        HttpInputStream.fill(HttpInputStream.java:512)
.at com.ibm.ws.webcontainer.srt.http.HttpInputStream.
        skip(HttpInputStream.java:450)
.at com.ibm.ws.webcontainer.srt.http.HttpInputStream.
        finish(HttpInputStream.java:161)
.at com.ibm.ws.webcontainer.srt.http.HttpInputStream.
        close(HttpInputStream.java:493)
.at com.ibm.ws.webcontainer.srt.SRTServletRequest.
        finish(SRTServletRequest.java:1786)
.at com.ibm.ws.webcontainer.srt.SRTConnectionContext.
        finishConnection(SRTConnectionContext.java:80)
.at com.ibm.ws.webcontainer.WebContainer.handleRequest
        (WebContainer.java:1005)
.at com.ibm.ws.webcontainer.WSWebContainer.handleRequest
        (WSWebContainer.java:1566)
.
To verify, you can ask for the following traces:
Would it be possible to gather these traces:

TCPChannel=all:ZAioTCPChannel=all:HTTPChannel=all:
XMemChannel=all:com.ibm.ws.webcontainer.*=all:
GenericBNF=all
.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 for z/OS                        *
****************************************************************
* PROBLEM DESCRIPTION: network io errors may cause xmem        *
*                      thread hanging on proxy server for z/OS *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Under certain network io error conditions, xmem thread in
proxy might hang because of missing notification of error
conditions.

Problem conclusion

Code has be modified such that the missing notification
is generated in the proxy and sent to the xmem channel. The
hanging issue of xmem thread is fixed.

APAR PM05685 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.13 of WebSphere Application Server V7.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
PM05685
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
2010-01-21
Closed date
2010-04-14
Last modified date
2010-11-02

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 UK61114
UP10/10/21 P F010

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":"BU053","label":"Cloud & Data Platform"},"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:
25 October 2021

Tips

PM05685: HTTP RESPONSE NOT FLUSHED ON Z/OS AND THE HTTP PROXY HAS STOPPED READ ON THES CONNECTION

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 UK61114

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?