PQ76884: WEB CONTAINER IGNORES THE ERROR THAT WAS LOGGED BEFORE CAUSING INCOMPLETE POSTING DATA OF THE POST REQUEST.

 A fix is available

PQ76884; 4.0.7: Servlet processes incomplete post data.



APAR status
Closed as program error.

Error description
When the transfer of the data  of the POST http request is
not completed for some reasons, such as I/O timeout, WebSphere
Web container logs this problem but does not take an
appropriate action.

Instead of returning an appropriate return code
to the plug-in, WebContainer continues processing
the http POST request resulting that the response is
based on processing the incomplete data of the POST http
request.

Stack trace has the following:
java.io.InterruptedIOException:
Read timed out
 at java.net.SocketInputStream.socketRead(Native Method)
 at
java.net.SocketInputStream.read(SocketInputStream.java(Compiled
Code))
 at com.ibm.ws.io.Stream.read(Stream.java:17)
WebContainer returns 200 status code to the plug-in
& to the client invoking a feeling that the request was
processed properly but it was not.
.
This situation might occur when trafic is heavy & mostly but
not necessarily over slow networks, such as modem connections
or ISDN lines.
In the past the APAR 
PQ76013 for WebSphere 5.0 was created
for the same problem.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of POST   *
*                 method.                                      *
****************************************************************
* PROBLEM DESCRIPTION: When transferring data for the POST, if *
*                      an http request can not be completed    *
*                      for some reasons, such as I/O timeout,  *
*                      Web container logs this problem but     *
*                      does not take an appropriate action.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When InterruptedIOException occurs, the exception was caught
but ignored, and thus, processing continues with partially
received post data. This may cause a servlet response to be
incorrect.
Problem conclusion
Up on InterruptedIOException, if web container is unable to
retrieve all post data correctly, the request is bad due to
timeout. Thus a Request Timeout error code should be sent back
to the client, if the connection still can be used.

In case of large post data from client, servlet should pay
special attention on how to catch and handle
InterruptedIOException, otherwise,  web container will send 408
error.
Temporary fix
This fix is the same as 
PQ76013 for V5.
Comments
APAR information
APAR number PQ76884
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-07-29
Closed date 2003-12-01
Last modified date 2003-12-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WEBENG          

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 #: PQ76884
IBM Group: Software Group
Modified date: Dec 1, 2003