On Fri, 7 Apr 2023 16:09:06 GMT, Alan Bateman wrote:
> Perhaps the issue summary / PR title should be more like this?
I'm not so sure. What you suggest describes this fix for this bug, but it
doesn't really describe the bug itself - instead, the bug argues that the
reentrant behavior is wrong
On Fri, 7 Apr 2023 15:53:10 GMT, Brian Burkhalter wrote:
> Perhaps the issue summary / PR title should be more like this?
>
> ```
> Clarify reentrant behavior of the close method of FileInputStream,
> FileOutputStream, and RandomAccessFile
> ```
or better still, create a new issue in JBS as
On Fri, 7 Apr 2023 14:16:32 GMT, Archie L. Cobbs wrote:
>> IO stream classes like `FileOutputStream` can have assocated NIO channels.
>>
>> When `close()` is invoked on one of these classes, it in turn invokes
>> `close()` on the associated channel (if any). But when the associated
>>
> IO stream classes like `FileOutputStream` can have assocated NIO channels.
>
> When `close()` is invoked on one of these classes, it in turn invokes
> `close()` on the associated channel (if any). But when the associated
> channel's `close()` method is invoked, it in turn invokes `close()` on
