hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: Stale connection checking with NIO
Date Mon, 18 Nov 2013 09:44:58 GMT
On Mon, 2013-11-18 at 07:42 +0530, Asankha C. Perera wrote:
> Hi Oleg
> To a previous reply [1] on this list you said: "The stale connection 
> check is needed for blocking connections only as the blocking I/O model 
> provides no way of finding out whether a connection is half-closed 
> unless a attempt is made to read from the underlying socket. 
> Non-blocking connections can immediately react to I/O events due to 
> their asynchronous nature and can either be open or closed, but never 
> stale."
> We are seeing something very similar to a stale connection when we try 
> to re-use a keep-alive connection. Although I still do not have a TCP 
> dump to prove this, at a theoretical level isn't is possible for a NIO 
> connection kept alive to be stale at the point of it being re-used?

Hi Asankha

As long as the underlying channel has input interest turned on it should
get notified of the opposite end closing the connection. NIO connections
can only become 'stale' if one explicitly disables input interest prior
to releasing connections back to the pool.

I hope this helps


> thanks
> asankha
> [1] http://markmail.org/message/okuhqdcqgkavmhta

To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message