Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Consider the following invocation sequence:
1. writer writes a lot of bytes
2. writer closes the OutputStream
3. reader comes in and starts reading
4. it reaches EOF
5. reader closes InputStream
The current implementation doesn't distinguish #2 above with InputStream.close(), so in this call sequence, the reader incorrectly gets IOException("Pipe closed") instead of successfully reading data.