APAR status
Closed as program error.
Error description
The "InterruptedIOException: Read timed out" event is
not being logged in the AppServer logs if a read error
occurred. This kind of event usualy happens on a slow POST.
Since an I/O exception can be a normal event, I am not
absolutely sure if we have to log this exception in the
AppServer logs. When getParameter type of API encounters
an InterruptedIOException if a read timed out, these APIs
do not throw any exception per servlet 2.3 spec so we can
not not use a RuntimeException. Usualy a developer of the
application (EAR) should take care of an incomplete POST
parameters (such as redirect the client to an appropriate
resource, etc ...) when a read timed out event occured when
reading the POST parameters.
.
Currently we log this exception in FFDC logs so it would
make sense to log it also in the SystemErr logs. It will
help to our customers & WebSphere support if this
exception is logged in AppServer logs so that
a WebSphere Administrator is aware of this event &
can take an appropriate action, such as to increase
ConnectionIOTimeOut custom property in WebSphere
Web container (default is 5 seconds).
This APAR was opened against WebSphere 5.0 releases.
Local fix
The InterrupterIOException exception is not being logged,
WebSphere administartor can find out that this event occured
only when they enable ServletEngine & HTTP Transport trace,
or if they application handles incomplete POST data scenario.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Web Applications on a slow *
* network *
****************************************************************
* PROBLEM DESCRIPTION: When InterruptedIOException occurs *
* during processing a request, the error *
* is logged in FFDC only. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Should add the exception log in System.Out.
Problem conclusion
The exception is logged in System.Out as well as FFDC.
The fix will be included in 5.0.2.10 and 5.1.1.3.
Please check the recommended updates page:
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP
&uid=swg27004980
for delivery dates.
Temporary fix Comments
APAR information |
APAR number |
PQ95938 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-10-19 |
Closed date |
2004-11-30 |
Last modified date |
2005-05-05 |
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 |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|