JDK-4730518 : getInputStream() simply hangs under sokme conditions
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 1.4.0_01
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_2.6
  • CPU: generic
  • Submitted: 2002-08-13
  • Updated: 2002-08-13
  • Resolved: 2002-08-13
Related Reports
Duplicate :  
JDK-4143518 - Need ability to set socket options on URLConnection
Description
When a servlet running on Tomcat fails during initialization, it simply hangs,
neither terminating nor running. (The base bug).

When the client attempts to connect to the servlet using UrlConnection, getOuputStream() appears to succeed, but getInputStream() simply hangs,
as well.

The client application is therefore unable to detect the upstream error and
deliver an error message to the user.
Comments
EVALUATION Programmantic control of the timeouts used by the protocol handlers is on the list for tiger - see 4143518. As a workaround the sun.net.client.defaultConnectTimeout and sun.net.client.defaultReadTimeout system properties can be used to configured global connect & read timeouts. ###@###.### 2002-08-13
13-08-2002