MQSeries.net :: View topic

narendra · Posted: Thu Aug 22, 2002 3:28 am Post subject:

Hi,

Database error: SQL State '40003'; Native Error Code '-30081'; Error Text '[IBM][CLI
Driver][DB2] SQL30081N A communication error has been detected. Communication
protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Locat
ion where the error was detected: "". Communication function detecting the erro
r: "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001: EID
C.6280f5ba-ec00-0000-0080-d425ba7c6bf1: /build/S210_P/src/DataFlowEngine/ImbOdbc
.cpp: 234: ImbOdbcHandle::checkRcInner: :

we experienced this problem with WQMI 2.1 with CSD0002.
Our WMQI 2.1 and MQSeries 5.2.1 are all in one windows2000 box
We have a compute node which pulls data from a DB2 database on an AIX machine.
During the night the DB2 on AIX was backup so the DB2 connection to the message was cut.
We noticed that, the compute node always fail the first time in the morning when we try to run the msg.
Immediately after the failure, if we put again, it always work.

It appears that, once the DB2 connection to the msg flow was cut, the msg flow will go into
'sleep' mode and if you put something in the MQInput node while the DB2 connection is closed, the
compute node will fail BUT it will reestablish the DB2 connection again for the msg so the next time the
msg is run, it is ok. It seems to be a WMQI problem.

here is how we test this.

step1 logon to DB2 server dbase
db2 list applications
db2 force application (application id for DataFlow Engine)

step2 put msg on the MQinput queue. This will fail at the compute node
step 3 logon to DB2 server dbase and there is still NO connection
step4 put the SAME msg again , and it works
step5 logon to DB2 and the connection is established

from this test, we think it is an MQSI problem.

Thanks in advance
Narendra