You don't say what OS your running DB2 on, but as an example AIX has a keep alive parms for those connections which defaults to 2 hours and will only disconnect from DB2 after that. You would need to change that parm down, but that would affect other network connections on you box too.
I think you may have to look at this problem from the websphere perpective also ... When websphere timesout its connections, I would assume that it issues a disconnect to the database before timing out ... If it has not been issued, db2 server will assume that the client is still active because it as not recevied a disconnect
Visit the new-look IDUG Website , register to gain access to the excellent content.
We are using Windows 2000 Service Pack 4 . Infact i waited 8 hours to see whether connections are getting timed out in DB2 , it never happened . The moment connections getting timed out in Websphere i can see the number of socket connections made to the DB2 box coming down to the same number as the connection pool size .
For example :
Webshpere connection pool size : 10
Netstat -a shows me 10 socket conenctions .
but DB2 list applications gives me 24 [ Remains 24 for days ] .