JDK-1267037 : java.io.Piped*Stream specification does not describe unconnected streams
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 1.0.2
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_2.5
  • CPU: sparc
  • Submitted: 1996-09-09
  • Updated: 1999-01-15
  • Resolved: 1999-01-15
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
1.2.0 1.2beta4Fixed
Related Reports
Duplicate :  
JDK-1267038 - java.io.PipedOutputStream.write(b) method does not work with unconnected streams
Description

Name: saf@russia			Date: 09/09/96


This bug was found by St.Petersburg Java SQE team (by Stanislav Avzan).

The Java Language specification (Version 1.0 - August 1, 1996) does not describe
behaviour of java.io.PipedInputStream/PipedOutputStream class methods in case
of unconnected streams.

In fact, unconnected PipedInputStream behaves as empty connected closed from 
PipedOutputStream side PipedInputStream eg. any reading returns -1 (EOF marker).

Unconnected PipedOutputStream throws NullPointerException by any writing.

We suppose both PipedInputStream and PipedOutputStream should throw IOException
in case of unconnected streams. If so, source code revision should be made.

Workaround:
None
======================================================================
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 1.2beta4 INTEGRATED IN: 1.2beta4
14-06-2004
EVALUATION Coding error. Added checks for unconnected streams. The JLS spec has been folded into the doc comments in this class; the doc comments assert that an IOException should be thrown when reading from or writing to an unconnected stream. ###@###.### 1998-03-09
09-03-1998