-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jan Hlavat� wrote:
>Did you try setting SO_KEEPALIVE socket option using
Socket.setKeepAlive(boolean)?
>That what its for. The timeout may be really long though (sbout 2 hours),
>but may be tuned on OS level (globally).
Yes, I tried setKeepAlive but the timeout was too long and I didn't know
I had to set it in the OS. Thanks for the info on that. It seems less
than optimal because it would affect other applications as well, but
maybe that's ok.
I was thinking maybe the best approach would be to.
1) Fix network server to use setKeepAlive so setting the system
keepalive timeout will affect it.
2) Add a db2j.drda.connTimeout property so users can set an absolute
limit on connection life. Connections would timeout after this limit
regardless of whether there was connectivity.
Thoughts?
Kathey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBaCi5G0h36bFmkocRAsd+AKCS8lAgjGZ7jONrASlWSUmpRogvlQCglOrL
FbNUxtWg8uCrQ6ouoQJwf+s=
=RSC5
-----END PGP SIGNATURE-----
