Fixes are available
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4
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
Document Information
Modified date:
04 May 2022