PK89992: TRANSFER OF QUERY PARAMETERS VIA THE PORTLET REQUEST DISPATCHER TO A SERVLET FILTER DURING THE ACTION PHASE MAY NOT WORK CORRECT

Fixes are available

APAR status

Closed as program error.

Error description

Transfer of query parameters via the portlet request dispatcher
to a servlet filter during the action phase may not work
correctly.

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application Server
****************************************************************
* PROBLEM DESCRIPTION: Query string passed into a portlet      *
*                      request dispatcher cannot be received   *
*                      by servlet filter                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using a PortletRequestDispatcher-Include with a path
containing a query string, the new parameters provided are not
present in a servlet filter triggered within processAction on
WebSphere Portal V6.1. In WebSphere Application Server V7.0 it
works and also on WebSphere Portal V6.1 when only a render
request has been processed before.

Problem conclusion

The PortletRequestImpl does a lazy initialization of its
parameter map and caches it until an update is triggered. The
ServletInvocationListener registered with the portlet
container does such an update, but the event happens after
Servlet filters have been run through. In the case of Portal
V6.1 there is an ActionListener that invokes
PortletRequest.getParameter() which triggers the internal
initialisation and caching of the parameter map, so that in
action phase the parameter map is already cached when queried
for the first time in a servlet filter or portlet. This makes
the difference to plain WebSphere Application Server V7.0 and a
render-only request.

To solve the problem, the ServletInvocationListenerImpl now
also listens to FilterInvocationEventsand and does precisely
the same as it did already on servlet invocations.


The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK89992
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-26
Closed date
2009-07-08
Last modified date
2009-07-08

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK89992: TRANSFER OF QUERY PARAMETERS VIA THE PORTLET REQUEST DISPATCHER TO A SERVLET FILTER DURING THE ACTION PHASE MAY NOT WORK CORRECT

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

R700 PSY

Document Information

Share your feedback

Need support?