This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
IOException thrown when a read from a FastJ8SocketChannel fails due to the underying channel being closed #214
Comments
nicktindall
added a commit
that referenced
this issue
Oct 11, 2022
…e to underlying being closed. Fixes #214
nicktindall
added a commit
that referenced
this issue
Oct 27, 2022
…e to underlying being closed. Fixes #214
nicktindall
added a commit
that referenced
this issue
Oct 27, 2022
…e to underlying being closed. Fixes #214
nicktindall
added a commit
that referenced
this issue
Oct 27, 2022
…e to underlying being closed. Fixes #214
nicktindall
added a commit
that referenced
this issue
Oct 27, 2022
…e to underlying being closed. Fixes #214
nicktindall
added a commit
to OpenHFT/OpenHFT
that referenced
this issue
Oct 27, 2022
nicktindall
added a commit
to OpenHFT/OpenHFT
that referenced
this issue
Oct 27, 2022
nicktindall
added a commit
to OpenHFT/OpenHFT
that referenced
this issue
Oct 27, 2022
|
Released in Chronicle-Network-2.24ea1, BOM-2.24ea6 |
|
Released in Chronicle-Network-2.23.23, BOM-2.23.131 |
|
Released in Chronicle-Network-2.22.16, BOM-2.22.165 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It should throw
ClosedChannelExceptionlike the other implementations do (this is handled in lots of places)The text was updated successfully, but these errors were encountered: