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, such as sending 408 (SC_REQUEST_TIMEOUT) return code
to the plug-in & to the client. Instead of the returning an
appropriate return code to the plug-in, WebContainer continues
procesing the http POST request resulting that the response is
based on processing the incomplete data of the POST http
request. 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.
.
In AppServer FFDC log (under ffdc folder) you can see this type
of error:
------Start of DE processing------ = [03.05.29 13:35:48:062 JST]
key = java.io.InterruptedIOException
com.ibm.ws.webcontainer.servlet.RequestUtils.parsePostData 398
Exception = java.io.InterruptedIOException Source =
com.ibm.ws.webcontainer.servlet.RequestUtils.parsePostData
probeid = 398
Stack Dump = 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)
In servlet engine trace at the same time frame you can see this
exception:
SRTServletReq d IOException occured in reading of post data..
skip attempt in finish method
.
No errors in AppServer stdout & stderr logs that makes
tracing of this problem quite difficult. Only servlet
engine trace clearly showed always IOException.
.
L3 ENG will need to review also WebSphere 4.0 code
to verify that the same problem is not in WebSphere 4.0
release.
Local fix
N/A
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of a *
* dial-up connection to post a large amount *
* of data to a server. *
****************************************************************
* PROBLEM DESCRIPTION: The WebAppDispather still delivers the *
* request with incomplete data for *
* processing when an *
* IOInterruptedException occurred. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an IOInterruptedException occurred during the reading of
post data, the WebAppDispatcher still dispatches the request for
processing with incomplete data.
Instead an " Error code 408 - request time out " should be sent
to client.
Problem conclusion
The code was modified so that upon an IOInterruptedException
when reading a request, an error page is sent to the client with
an error code 408 - Request timeout.
Temporary fix
ZE Fix Error
PQ84897 04/02/18
ZE Fix Error
PQ85830 04/03/10
testFix posted.
Comments
APAR information |
APAR number |
PQ76013 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-07-03 |
Closed date |
2003-08-27 |
Last modified date |
2004-03-10 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|