APAR status |
Closed as program error.
| Error description
During the RequestDispacher.forward, request parameter given in
the foward path query string are not being merged with the exist
ing request parameter. Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who *
* use dynacache. *
* *
****************************************************************
* PROBLEM DESCRIPTION: When using dynacache, the request *
* parameter given in the forward path *
* query string is not being merged *
* with the existing request parameters. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When running WebSphere Application Server with dynacache
turned on, during a RequestDispatcher.forward the request
parameter given in the forward path query string is not being
merged with the existing request parameters.
Existing request parameters remain intact. The expectation is
to have the query parameters merged.
(Java Servlet Specification, SRV.8.1.1). Problem conclusion
The saving and restoring the parameters for proxied request has
been done for both webappdispatcher request as well as for the
CacheProxyRequest. Temporary fixComments
APAR information | APAR number | PQ59041 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-03-14 | Closed date | 2002-03-21 | Last modified date | 2002-03-21 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|