On 21 Apr 2010, at 11:28, galder(a)redhat.com wrote: > Hi, > > As a result of https://jira.jboss.org/jira/browse/ISPN-385, I'm adding a new command line parameter to the Hot Rod server that allows users to set an idle timeout. The effect of this timeout is that if a Hot Rod server has not received any commands from a given connection within that timeout, it will close it. The aim of this timeout is to battle against clients that might be sending partial or incomplete operations. Closing this connections allows for such incorrect ops to be discarded. > > If you pass 0, the idle timeout is disabled. By default, I have set the timeout to 1 minute but I wonder whether it's too low, or whether 0 would be a better default. The reason I say this is cos partial or incomplete operations is more of an edge case than the norm. Once the clients have been debugged, this should not be the norm, hence why I'm wondering whether 0 would be a better default. Well, it could be a DOS attack so 0 is not a good default. :)

> Also, any idle timeout settings would need to take in account client settings, or viceversa. There's no much point on a client pooling connections and setting idle timeout to 2 minutes when the server will close idle connections after 1 minute. Keepalives? Wasn't there a mechanism for clients to ping the server to keep a connection alive?

-- Manik Surtani manik(a)jboss.org Lead, Infinispan Lead, JBoss Cache http://www.infinispan.org http://www.jbosscache.org _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev