Cached thread pools going away

Bruno de Carvalho kindernade at gmail.com
Fri May 20 10:57:51 EDT 2011


Pardon the slight offtopic, but a periodic PING command wouldn't be a bad idea to keep the connection alive.
You could use an IdleStateHandler with a HashedWheelTimer; whenever the IdleStateHandler detected incoming/outgoing inactivity over a configurable threshold, it'd fire a PING command.


Cheers,
  Bruno



On May 20, 2011, at 3:48 PM, Jeff G. wrote:

> Marc-André,
> 
> Thanks for replying.  After a LOT of poking around and attaching debuggers,
> etc., I discovered that Redis is timing out my client connections after five
> minutes of inactivity (which turns out to be the default behavior, but you
> won't know that unless you read the source code, since the documentation is
> rather sparse).  Disabling the server-side timeout in Redis fixed the
> problem.
> 
> Best,
> Jeff
> 
> 
> 
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Cached-thread-pools-going-away-tp6378919p6386355.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> 
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users




More information about the netty-users mailing list