In some race scenarios, such as the one tested by UNDERTOW-2212 PR, depending on the order the threads close the connection, we could end up getting a ClosedChannelException at the resulting exchange, or get an IOException with "Invalid connection state" at the callback as an error.

Maybe it is a good idea to use the same ClosedChannelException for both scenarios.