> Have anyone seen this before.., we are seeing a lot of orpahn DB2
> connections when the client terminates abnormally?
> should'nt the underlying TCP/IP mechanism terminate the connection? or is
> there any setting in DB2 that I need to change.
If these are Windows clients it's a pretty common problem. Windows sockets
library does not automatically shutdown the task's connections when a
process terminates. So, if the programmer did not trap the exit request and
explicitely shutdown the TCP connections, the DB server will still see them
until the local TCP stack times out the connections as inactive. Depending
on the OS the server is running on (some OS's have tuning parameters in the
TCP/IP setup) this can take from 10 minutes to over an hour.
Art S. Kagel
Brian Tkatch - 30 Jan 2006 15:17 GMT
Would TERMINATE be of any help?
B.