db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Thalamati <tsur...@Source-Zone.org>
Subject Re: [VOTE] Re: Help detecting client disconnects for network server
Date Mon, 11 Oct 2004 23:30:03 GMT

Which one of the following properties have higher precedence ?   For
example if  user sets  derby.drda.keepAlive = true  (Assume 2 hours on a
platform)  and derby.drda.connSoTimeout=  1hour., Connection is going to
be terminated after 2 hours or 1hour ?

Thanks
-suresht


Kathey Marsden wrote:

> Samuel Andrew McIntyre wrote:
>
> >So, I'm still not sure that I like having keepalive set by default
> >without a way to turn it off.
>
>
> OK, so, given the input from everyone I submit the following solution to
> vote:
>
>
> 1) Have keepAlive on by default. It seems important not only for locks
> but for potential network server bloat due to connections not getting
> cleaned up.
>     
>
> 2) Add a property derby.drda.keepAlive={true|false} (defaults to true as
> described above).  There seems to be a need to be able to turn keepAlive
> off in some cases.
>     
>
> 3) Add property derby.drda.connSoTimeout=<milliseconds> (defaults to 0,
> infinite) to provide the ability to have connections timeout after a
> period of inactivity. The connections will still timeout, even if the
> connection is working fine but will timeout after blocking on a read for
> this length of time.   I am about +.5 on this one.  It would be nice to
> provide the capability, but hesitate to add yet another property.
>
>
>
> Kathey
>
>
>
>     
>
>
>
>

Mime
View raw message