idle or dead connection

[xeaon]

I have developped a client/server application. the server side of this app. is a asp.net webservice that connect to db2 database via a COM build by ACCPAC (the accounting software).

My app. run perfectly untill , for some reason, a build up of dead connection occur.

Since i don't have a quick responce from ACCPAC, i'm wondering if there ia way that this problem occur because of setting in db2, like low mem or not enought delay timeout...?!?!

here some information of one of those dead connection(idle for 4 hour and counting some are there for days until i reboot...)

PLATEFORM IS WIN2K SERVER
USING : GET SNAPSHOT FOR APPLICATION AGENTID 103

Application handle = 103
Application status = UOW Waiting
Status change time =
Application code page = 1208
Application country/region code = 1
DUOW correlation token = *LOCAL.DB2.00F6C1180044
Application name = aspnet_wp.exe
Application ID = *LOCAL.DB2.00F6C1180044
Sequence number = 0002
TP Monitor client user ID =
TP Monitor client workstation name =
TP Monitor client application name =
TP Monitor client accounting string =

Connection request start timestamp = 10-21-2003 14:00:51.145036
Connect request completion timestamp = 10-21-2003 14:00:51.150908
Application idle time = Not Collected
Authorization ID = DB2ADMIN
Client login ID = ASPNET
...
...
...


If someone ave any idea !!!!

thanks

 

[blom0344]

I have the same experience with an ETL tool that occasionally builds up connections without disconnecting them. For this tool it happens infrequently, so I use the force command to disconnect the agentid manually. Other applications (using all CLI/ODBC) disconnect like they should.
In case of the ETL-tool is appears to be a bug on the tool side, not a DB2 setting that can be adjusted.

I am sure that with the DB2 Governor you should be able to create a rule to disconnect agentid's that are in idle mode for some time (for a given application name)

T. Blom
Information analyst
tbl@shimano-eu.com