PI28910: Web container call to AsynContext.dispatch() causes all subsequent calls of request.isAsyncStarted()) to return false

Fixes are available

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

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

Document Information

Modified date:
28 April 2022

Tips

PI28910: Web container call to AsynContext.dispatch() causes all subsequent calls of request.isAsyncStarted()) to return false

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?