Fixes are available
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
The Java Servlet 3.0 Spec states "public boolean isAsyncStarted() - Returns true if async processing has started on this request, and false otherwise. WebSphere Application Server Web Container Call to asyncContext.dispatch() causes all subsequent calls of request.isAsyncStarted() to return false. It should be the case that isAsyncStarted() returns true if async processing has started and false otherwise. We found some calls to isAsyncStarted() return false when the async propcessing has been started.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Full * * Profile version 8.5.5 and Liberty Profile * * version 8.5.5 users of WebContainer. * **************************************************************** * PROBLEM DESCRIPTION: ServletRequest.isAsyncStarted() * * incorrectly returns false on a * * thread after AsynContext.dispatch() * * has been called. * **************************************************************** * RECOMMENDATION: * **************************************************************** After a thread, which has started async, invokes javax.servlet.AsynContext.dispatch(), any call to javax.servlet.ServletRequest.isAsyncStarted() returns false. The correct behavior is to return true on that thread until the dispatch takes effect, at that moment it should start returning false.
Problem conclusion
The WebContainer code was modified to return the correct value. The fix for this APAR is currently targeted for inclusion in fixpacks 8.0.0.11 and 8.5.5.5. 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
PI28910
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-03
Closed date
2015-02-04
Last modified date
2015-02-04
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022