Message10881

Most likely the solution here is to prevent early closes by validating data has been flushed, via flush notifications.

My reading of C socket semantics is that send simply means the data was copied over to the kernel for actual network send; this seems no different than it being copied over to Netty. But perhaps we can upgrade to 4.1 (perhaps easy); and use this API http://netty.io/4.1/api/io/netty/channel/Channel.html#bytesBeforeUnwritable() to get a more reliable estimate than the blind try to send all bytes into Netty that is done now.