This bug is submitted to track a discussion on core-libs-dev:
http://mail.openjdk.java.net/pipermail/core-libs-dev/2011-January/005732.html
In summary, BufferedWriter#close will fail with IOException and leave the stream open in the event that the close of the underlying Writer fails. BufferedReader has the same issue.
A related issue is that FilterOutputStream#close doesn't propogate the exception from the flush if it fails when closing the stream.
http://mail.openjdk.java.net/pipermail/core-libs-dev/2011-January/005732.html
In summary, BufferedWriter#close will fail with IOException and leave the stream open in the event that the close of the underlying Writer fails. BufferedReader has the same issue.
A related issue is that FilterOutputStream#close doesn't propogate the exception from the flush if it fails when closing the stream.
- duplicates
-
JDK-7030769 FilterOutputStream ignores IOException from flush() in close()
-
- Closed
-
-
JDK-7122163 BufferedOutputStream.close does not throw IOException on error
-
- Closed
-
-
JDK-6390383 (spec) FilterOutputStream.close() silently ignores flush() exceptions
-
- Closed
-
- relates to
-
JDK-7077254 Audit and fix classes in java.io for cases where close may fail
-
- Open
-
-
JDK-8054565 FilterOutputStream.close may throw IOException if called twice and underlying flush or close fails
-
- Closed
-