PQ80612: getParameter method of SRTServletRequest class should be null in the beginning of the request.

 Fixes are available

5.1.0.5: WebSphere Application Server Express 5.1 Cumulative Fix 5
5.0.2.7: WebSphere Application Server Express 5.0.2 Cumulative Fix 7
5.1.1: WebSphere Application Server Version 5.1 Fix Pack 1 (Version 5.1.1)
5.0.2.12: WebSphere Application Server 5.0.2 Cumulative Fix 12
5.0.2.13: WebSphere Application Server 5.0.2 Cumulative Fix 13
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for AIX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Solaris
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for HP-UX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Windows
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Windows
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for AIX
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Solaris
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Windows
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.8: WebSphere Application Server V5.0.2 Cumulative Fix 8
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX



APAR status
Closed as program error.

Error description
getParameter method of SRTServletRequest
class should be null in the beginning of the request, and it is
initialized into finish method at the previous request, then
the _parameters would be null at the end of previous request.
But in this case, the java.lang.NumberFormatException was thrown
at getContentLength in the previous request and the _parameters
would not be initialized.


 11/09/03 06:45:10:489 UTC  7dafda30 WebGroup      X Servlet
Error:
Error while finishing the connection:
java.lang.NumberFormatException:
  at java.lang.Integer.parseInt(Integer.java(Compiled Code))
  at java.lang.Integer.parseInt(Integer.java(Compiled Code))
  at
com.ibm.ws.http.HttpRequest.getContentLength(HttpRequest.java:18
9)
  at
com.ibm.servlet.engine.http11.HttpConnection.getContentLength(Ht
tp
  at
com.ibm.servlet.engine.srp.SRPConnection.getContentLength(SRPCon
ne
  at
com.ibm.servlet.engine.srt.SRTServletRequest.getContentLength(SR
TS
  at
com.ibm.servlet.engine.srt.SRTServletRequest.finish(SRTServletRe
qu
  at
com.ibm.servlet.engine.srt.SRTConnectionContext.finishConnection
(S

This is because the finish method of SRTServletRequest only to
catch
the IOException and the other exception such as
NumberFormatException is thrown.

If the exception was occured into finish method, the
_parameters isn't initialized to null and the _parameters will
not be null in the beginning of next request. So the incorrect
parameter returned from getParameter(). The _parameters should
be initialized into finally.
Local fix
no work around
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users with      *
*                 applications sending multiple requests with  *
*                 some requests causing exceptions in the      *
*                 webContainer during the completion handling  *
*                 of such requests.                            *
****************************************************************
* PROBLEM DESCRIPTION: In a multiple request scenario, when    *
*                      the first request is completed, the     *
*                      internal request parameters are         *
*                      supposed to reset to their intial       *
*                      values for the next request.  However,  *
*                      if an exception is occurred when        *
*                      completing the first request, these     *
*                      parameters are not reset.               *
*                      As a result, the old values of these    *
*                      internal request parameters will be     *
*                      used for second request.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Servlet request code should reset all internal parameters
even if an exception is encoutered.
Problem conclusion
Modify the Servlet request code to reset all internal
parameters after the exception is handled.
Temporary fix
testFix driver posted to 
pq99999 on 11/14/2003
Comments
APAR information
APAR number PQ80612
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-11-07
Closed date 2004-01-06
Last modified date 2004-01-06

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ENGINE          

SRLS

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ80612
IBM Group: Software Group
Modified date: Jan 6, 2004