I support a .Net application running on a SERVER accessing MF Db2
data. Occasionally, we have some type of connection problem that we
have been unable to debug up to this point. We typically receive one
of these IBM.Data.DB2.DB2Exception messages:
ERROR [40003] [IBM][CLI Driver] SQL30081N A communication error has
been detected. Communication protocol being used: ‘TCP/IP'.
Communication API being used: ‘SOCKETS'. Location where the error was
detected: ‘138.83.176.1'. Communication function detecting the error:
‘recv'. Protocol specific error code(s): ‘10053', ‘*', ‘*'.
SQLSTATE=08001
This corresponds to some messages in the DB2 started task running on
the MF:
10.30.57 STC11095 DSNL511I -DB2C DSNLIENO TCP/IP CONVERSATION FAILED
866
866 TO LOCATION 112.64.103.172
866 IPADDR=112.64.103.172 PORT=2655
866 SOCKET=RECV RETURN CODE=1121 REASON
CODE=76650446
10.31.08 STC11095 DSNL511I -DB2C DSNLIENO TCP/IP CONVERSATION FAILED
032
032 TO LOCATION 112.64.103.172
032 IPADDR=112.64.103.172 PORT=3180
32 SOCKET=RECV RETURN CODE=1121 REASON CODE=76650446
Along with the Communication error exception, we typically also
receive some other exceptions during this time, mainly....
Inner Exception Type: IBM.Data.DB2.DB2Exception ;Inner Exception
Message: ERROR [08003] [IBM][CLI Driver] CLI0106E Connection is
closed. SQLSTATE=08003
So the communication problem (whatever it is) seems to manifest in the
first exception - Communication problem - and this must hose up some
of our connections so at that point, we begin to receive the
Connection is Closed message.
Our C# instansiates a DB2Connectin object and issues an open against
it. Then an executeNonQuery statement to run the SP. It is pretty
standard code and works nearly all the time. We think our problem is
load related - b/c we only encounter under productin load and more so
on our busiest servers.
Any help greatly appreciated.
Tim Reynolds
Verizon Data Services