2016-09-19 11:54 GMT+02:00 Avanish Kant <ak...@manh.com>:
> Extra bit of information that may help:
> One change that I did try is to change "Http11NioProtocol" to
> "Http11Nio2Protocol" just to see how it goes and noticed that this
> Exception is not thrown for NIO2.
> I am suspecting that I have hit some bug with "Http11NioProtocol" and
> appreciate any kind of help/tips you can provide.
> The problem was fixed and it will be in the next build, 8.5.6. NIO2
doesn't have the problem since the IO read EOF result didn't have any
special handling (so it was fatal).