PI76351: ServletRequest.getRequestURI() returns inconsistent results after AsyncContext.start().

Fixes are available

APAR status

Closed as program error.

Error description

For a request which is forwarded to another servlet which
then starts asynchronous processing and dispatches the
request to a runnable using AsyncContext.Start(), if the
started runnable  then calls ServletRequest.getRequestURI()
it can get one of two results:
1. The URI of the original request if the servlet returns
before the runnable calls getRequestURI().
2. The URI of the forwarded request if the runnable calls
getRequestURI() before the servlet returns.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - Web Container              *
****************************************************************
* PROBLEM DESCRIPTION: ServletRequest.getRequestURI() returns  *
*                      inconsistent results after              *
*                      AsyncContext.start().                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If an inbound request is forwarded to a servlet which then
starts asynchronous processing and dispatches the request to a
runnable using AsyncContext.Start(), if the started runnable
then calls ServletRequest.getRequestURI() it can get one of two
results:
1. The URI of the inboundl request if the servlet returns before
the runnable calls getRequestURI().
2. The URI of the forwarded request if the runnable calls
getRequestURI() before the servlet returns.

Problem conclusion

The WebContainer was changed to save request related data for a
runnable started with AsyncContext.start(), based on the values
when start() was called, such that the request data provided to
the runnable remain consistent. Request related data comprises:
URI, context path, servlet path, path info, query string and
dispatcher type.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.1.  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
PI76351
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-09
Closed date
2017-02-16
Last modified date
2017-02-16

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

R855 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":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI76351: ServletRequest.getRequestURI() returns inconsistent results after AsyncContext.start().

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

R855 PSY

Document Information

Share your feedback

Need support?