PQ80612: getParameter method of SRTServletRequest class should be null in the beginning of the request. | |||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||
![]() 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 aroundProblem 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/2003Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
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
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.