Give more context on CHANNEL_CLOSED_INBOUND when no native transport

[idelpivnitskiy]

Motivation:

When native transport is not used, users can see increased number of CHANNEL_CLOSED_INBOUND exceptions because Java NIO does not notify us about a closed connection until we make an attempt to write data.

Modifications:

• Provide more context for users when CHANNEL_CLOSED_INBOUND happens with no native transport available;

Result:

Users can get an idea where to look for the root cause for this use-case.