| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQBEGIN fails with mqrc 2128 after MQCOMMIT fails with 2003 |
« View previous topic :: View next topic » |
| Author |
Message
|
| klingelb |
 Posted: Wed Mar 05, 2003 1:58 pm Post subject: MQBEGIN fails with mqrc 2128 after MQCOMMIT fails with 2003 |
 |
|
Apprentice
Joined: 25 Sep 2002
Posts: 28
|
My Environment is the following:
My Hardware:
My Software Stack:
OS: AIX 5.1 ML2
MQSeries: V5.2 GM with CSD04
WMQI-B: V2.1 with CSD04
JRE: Java 1.3.0 with SR14
DB/2: V7.2 with FP7
My configuration:
Broker QM: QM1
Broker: BRKR1
DB2 instance owner: db2inst2
DB2 db that my flows access: RUNDB
The XA stanza in the qm.ini file of QM1:
XAResourceManager:
Name=DB2 RUNDB
SwitchFile=/usr/opt/mqsi/sample/xatm/db2swit
XAOpenString=RUNDB,db2inst2,password
ThreadOfControl=PROCESS
On the Control Center machine my flows have been deployed to BRKR1
with the "Coordinated Transaction" property checked ON.
Under high transaction volume scenarios, which occur only during peak
hours, on occasion there is a deadlock and one of my flows fails to
commit. This is not a problem, but when it tries to start a new
transaction it fails with mqrc 2128 UOW in progress. Now something
between MQ and WMQI was not cleaned up or reset. I'm not sure which,
but the broker BRKR1 fails ad infinitum to start a new transaction. From
what I've read the XACloseString is optional... is this true? I have tried
the dspmqtrn and rsvmqtrn commands, but according to MQ there are no
in doubt UOW. I have encountered the MQBEGIN fail with 2128 actually
many times and the only way to recover I have found is to stop BRKR1
there must be a better way. Any ideas?
My Sytem Log output:
Mar 1 14:38:50 eb3c WMQIv210[5136]: (BRKR1.SVTOU)[4370]BIP2232E: Error detected whilst handling a previous error in node 'SVT_ST.SetTimer.ThrowInsertTimerRecFailed'. : BRKR1.2b990ea0-f300-0000-0080d5b330423a: /build/S210_BP/src/DataFlowEngine/ImbDataFlowNode.cpp: 369: ImbDataFlowNode::logExceptionList: ComIbmComputeNode: b12a19e1-f100-0000-0080-ceaf0cdb891d.24e88c15-ed00-0000-0080-b9088e287155
Mar 1 14:38:50 eb3c WMQIv210[5136]: (BRKR1.SVTOU)[4370]BIP2230E: Error detected whilst processing a message in node 'SVT_ST.SetTimer.InsertTimerRec'. : BRKR1.2b990ea0-f300-0000-0080-e0d5b330423a: /build/S210_BP/src/DataFlowEngine/ImbDataFlowNode.cpp: 536: ImbDataFlowNode::createExceptionList: ComIbmComputeNo
de: b12a19e1-f100-0000-0080-ceaf0cdb891d.3bc0e577-ea00-0000-0080-d8c11a0c9c1c
Mar 1 14:38:50 eb3c WMQIv210[5136]: (BRKR1.SVTOU)[4370]DNIT6002E: Database error in node or message flow of type 'DniSetTimer'. Table: 'DNI.DNI_TIMER01', SQLCODE: -1, SQLSTATE: 57033, SQL native error: -913, SQL error text: '[IBM][CLI Driver][DB2/6000] SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code "2". SQLSTATE=57033 ': BRKR1.2b990ea0-f300-0000-0080-e0d5b330423a: /build/S210_BP/src/DataFlowEngine/ImbRdl/ImbRdlThrowExceptionStatements.cpp: 160: SqlThrowExceptionStatement::execute: ComIbmComputeNode: b12a19e1-f100-0000-0080-ceaf0cdb891d.3bc0e577-ea00-0000-0080-d8c11a0c9c1c
Mar 1 14:38:50 eb3c WMQIv210[5136]: (BRKR1.SVTOU)[4370]BIP2616E: Unable to commit an MQSeries transaction; MQCMIT failed; queue manager=QM1, MQCC=1, MQRC=2003. : BRKR1.2b990ea0-f300-0000-0080-
e0d5b330423a: /build/S210_BP/src/DataFlowEngine/ImbMqInputNode.cpp: 2630: ImbMqInputNode::mqCommit: ComIbmMQInputNode: 39bffc45-f100-0000-0080-bf81414a0e25
Mar 1 14:58:27 eb3c WMQIv210[5136]: (BRKR1.SVTOU)[4370]BIP2605E: Unable to start transaction coordinated by MQSeries; MQBEGIN failed; MQCC=2, MQRC=2128, broker node 'SVT_ST.SVT.SVT_ST', queue 'SVT.SVT_ST'. : BRKR1.2b990ea0-f300-0000-0080-e0d5b330423a: /build/S210_BP/src/DataFlowEngine/ImbMqInputNode.cpp: 770: ImbMqInputNode::readQueue: ComIbmMQInputNode: 39bffc45-f100-0000-0080
bf81414a0e25
Mar 1 14:58:47 eb3c last message repeated 4 times
Mar 1 14:58:52 eb3c WMQIv210[5136]: (BRKR1.SVTOU)[4370]BIP2605E: Unable to start transaction coordinated by MQSeries; MQBEGIN failed; MQCC=2, MQRC=2128, broker node 'SVT_ST.SVT.SVT_ST', queue 'SVT.SVT_ST'. : BRKR1.2b990ea0-f300-0000-0080-e0d5b330423a: /build/S210_BP/src/DataFlowEngine/ImbMqInputNode.cpp: 770: ImbMqInputNode::readQueue: ComIbmMQInputNode: 39bffc45-f100-0000-0080-bf81414a0e25
Mar 1 15:00:47 eb3c last message repeated 23 times |
|
| Back to top |
|
 |
| klingelb |
| Posted: Fri Mar 07, 2003 11:11 am Post subject: |
|
|
Apprentice
Joined: 25 Sep 2002
Posts: 28
|
After bumping up my db2 diaglevel to 4 I see the following message in my db2diag.log file
DIA1036C XA error with request type of "". Transaction was not found. |
|
| Back to top |
|
|
| acampbell |
| Posted: Tue Sep 16, 2008 7:00 am Post subject: Help? |
|
|
Newbie
Joined: 16 Sep 2008
Posts: 1
|
I am currently having the same problem it seems. I have installed HACMP on AIX 5.3 and Message Broker with fixpack 7.
Sep 15 15:54:44 b25aciwas04 user:err|error WebSphere Broker v6007[123416]: (WMB6.BASE)[9510]BIP2605E: Unable to start transaction coordinated by WebSphere MQ; MQBEGIN failed; MQCC=2, MQRC=2128, broker node 'ComIbmMQConnectionManager', queue manager 'B25ACIWAS04'. : WMB6.7630d70e-1c01-0000-0080-c0371b6214c1: /build/S600_P/src/DataFlowEngine/ImbMqManager.cpp: 3369: ImbMqConnection::mqBegin: ComIbmMQConnectionManager: ComIbmMQConnectionManager
Have you had any luck finding a solution?
Thank you! |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
