PI82296: AsyncContext.comple() fails when called from a readListener.

Fixes are available

APAR status

Closed as program error.

Error description

AsyncContext.comple() intermittently results in an FFDC when
called from a javax.servlet.readListener.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - Web Container              *
****************************************************************
* PROBLEM DESCRIPTION: AsyncContext.comple() intermittently    *
*                      results in an FFDC when called from a   *
*                      javax.servlet.readListener.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
An FFDC occasionally occurs when complete() is called from a
readListener:

Stack Dump = java.io.IOException: Request not read yet
    at
com.ibm.ws.http.channel.internal.inbound.HttpInboundServiceConte
xtImpl.getRequestBodyBuffer(HttpInboundServiceContextImpl.java:1
520)
    at
com.ibm.ws.http.channel.internal.inbound.HttpInputStreamImpl.che
ckBuffer(HttpInputStreamImpl.java:116)
    at
com.ibm.wsspi.http.ee7.HttpInputStreamEE7.isFinished(HttpInputSt
reamEE7.java:123)
    at
com.ibm.ws.webcontainer31.srt.SRTInputStream31.isFinished(SRTInp
utStream31.java:105)
    at
com.ibm.ws.webcontainer31.async.AsyncReadCallback.complete(Async
ReadCallback.java:107)
    at
com.ibm.ws.http.channel.internal.inbound.HttpInboundServiceConte
xtImpl.getRequestBodyBuffer(HttpInboundServiceContextImpl.java:1
609)
    at
com.ibm.ws.webcontainer31.async.listener.ReadListenerRunnable.ru
n(ReadListenerRunnable.java:61)
    at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
utor.java:1153)
    at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
cutor.java:628)
    at java.lang.Thread.run(Thread.java:785)

Problem conclusion

The problem occurs when the thread on which complete runs
overtakes the readListener thread from which complete was
called. To address the problem the
thread which runs complete is not started until the readListener
thread which called complete has returned.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.3.  Please refer to the Recommended Updates page for
delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI82296
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-05-30
Closed date
2018-02-22
Last modified date
2018-02-22

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
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

RCD0 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI82296: AsyncContext.comple() fails when called from a readListener.

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

RCD0 PSY

Document Information

Share your feedback

Need support?