PK14478; 5.1.1.7: Error java.net.sockettimeoutexception: timeout after PK08648
 Downloadable files
 
Abstract
Frequent "IOException: Read timed out" messages in the error or trace logs, especially from HttpRequest.finish().
 
Download Description
PK14478 resolves the following problem:

ERROR DESCRIPTION:
After applying 5.1.1.7, customer observes spate of IO Error java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:153)
com.ibm.ws.io.Stream.read(Stream.java:17)
com.ibm.ws.io.ReadStream.read(ReadStream.java:181)
com.ibm.ws.http.ContentLengthInputStream.read
(ContentLengthInputStream.java:48)
WASRUN read timed out SocketTimeoutException

LOCAL FIX:

PROBLEM SUMMARY

USERS AFFECTED:
All WebSphere® Application Server users at the V5.0.2.14 and V5.1.1.7 versions.

PROBLEM DESCRIPTION:
Frequent "IOException: Read timed out" messages in the error or trace logs, especially from HttpRequest.finish().


RECOMMENDATION:
None

If an exception occurs in HttpRequest.finish() while trying to clean up left over request data, the HTTP headers for the current request are not deleted. Since the HttpRequest object is pooled and reused, this causes subsequent requests to use HTTP headers from the previous request. The main error is that the previous request was a POST request that included some amount of data in the request body, thus the request included a Content-Length and possibly Expect "100 Continue" header. The two main errors this causes are:

First, the Application server will initially respond to the request with a '100 Continue' response which the plugin or client can interpret as the final response.

Second, the Application server will think that the request was supposed to include a request body due to the Content-Length header and try to read this during the finish phase of servlet processing and when cleaning up the connection from HttpRequest.finish(). These reads will time out and cause the errors described above.

PROBLEM CONCLUSION:
The processing in HttpRequest.finish() has been changed to insure that the HTTP headers from the current request are cleaned up.

The fix for this APAR is currently targeted for inclusion in fix pack V5.0.2.15 and V5.1.1.8.

Please refer to the recommended updates page for delivery information:
General/swg27004980.html
 
Prerequisites
Please download the UpdateInstaller below to install this fix.
 
URL LANGUAGE SIZE(Bytes)
UpdateInstaller US English 7250000
 
 
Installation Instructions
Please review the readme.txt for detailed installation instructions.
 
URL LANGUAGE SIZE(Bytes)
Readme US English 3319
 
Download package
What is DD?
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
PK14478_50214 11-16-2005 US English 10138 FTP DD
PK14478_5117 11-16-2005 US English 10137 FTP DD
PK14478_5117 11-16-2005 US English 10137 FTP DD
PK14478_5117_ND.jar 11/23/2005 US English 10155 FTP DD
PK14478_50214_ND.jar 11/23/2005 US English 10156 FTP DD
 
Technical support
Contact IBM Support using ESR (http://www-306.ibm.com/software/support/probsub.html), visit the WebSphere Application Server Support Web site (http://www.ibm.com/software/webservers/appserv/was/support/), or contact 1-800-IBM-SERV (U.S. only).
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
Problems (APARS) fixed
PK14478
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > HTTP Transport
Operating system(s): Windows
Software version: 5.1.1.7
Software edition:
Reference #: 4010941
IBM Group: Software Group
Modified date: Nov 30, 2005