JDK-5054016 : get the failure immediately when writing individual chunks over socket fail
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-05-27
  • Updated: 2014-04-25
  • Resolved: 2004-06-24
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b58Fixed
Related Reports
Relates :  
JDK-8041924 - [TESTBUG] sun/net/www/http/ChunkedOutputStream/checkError.java fails on some systems
Description
###@###.### 2004-05-27

J2SE Version (please include all output from java -version flag):
  java version "1.5.0-beta2"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta2-b50)
  Java HotSpot(TM) Client VM (build 1.5.0-beta2-b50, mixed mode)

Does this problem occur on J2SE 1.3, 1.4 or 1.4.1?  Yes / No (pick one)
  N/A

Bug Description:
  This is a request specific to Tiger chunked transfer capability
  for large uploads you added in Sun JVM 1.5.  Our observation has 
  been when doing large uploads [10MB-50MB] in chunked manner, and if 
  the socket on the server side is closed or dead in the midst of the upload,
  the client still is continuing to write on the dead socket without 
  checking if the socket is alive or not.  This means the client will 
  know of the failure and be able to provide feedback only after all 
  the 10MB-50MB content has been written.  It would be a good improvement 
  to get the failure and exception thrown immediately when writing individual
  chunks.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic tiger-rc FIXED IN: tiger-rc INTEGRATED IN: tiger-b58 tiger-rc
17-07-2004
EVALUATION I have been able to reproduce the problem. The cause is known. We have been using a PrintStream for the output. That class doesn't throw any exception, instead caller needs to call checkError() to check the state of the last write. Should fix for Tiger-rc. ###@###.### 2004-05-28
28-05-2004