ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » unable to start a new trxn after mq backout

Post new topic  Reply to topic
 unable to start a new trxn after mq backout « View previous topic :: View next topic » 
Author Message
klingelb
PostPosted: Thu Mar 06, 2003 1:32 pm    Post subject: unable to start a new trxn after mq backout Reply with quote

Apprentice

Joined: 25 Sep 2002
Posts: 28
My Environment is the following:

My Hardware:

    RS/6000


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
View user's profile Send private message
bower5932
PostPosted: Fri Mar 07, 2003 7:08 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
I've seen others with this problem. It has always appeared to be more DB2 (tuning) related. I'd suggest setting the db2diag level to 4 and seeing what is in the db2diag.log file.

I'm not sure that I got the db2 things above 100% correct....
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
klingelb
PostPosted: Fri Mar 07, 2003 7:12 am    Post subject: Reply with quote

Apprentice

Joined: 25 Sep 2002
Posts: 28
Do you think it has anything to do with WMQI?
Back to top
View user's profile Send private message
klingelb
PostPosted: Fri Mar 07, 2003 9:23 am    Post subject: db2diag.log file after bumping up the diaglevel to 4 Reply with quote

Apprentice

Joined: 25 Sep 2002
Posts: 28
After I get the deadlock and rollback the following is what I see in
the db2diag.log with diaglevel 4:

2003-03-07-10.54.55.801269 Instance:dniinst1 Node:000
PID:19766(db2agent (RUNDB)) Appid:0903AA44.D42D.030307163219
lock_manager sqlplnfd Probe:80 Database:RUNDB

Request for lock "REC: (2, 26) RID 00001A10" in mode ".NW" failed due to deadlock Application caused the lock wait is "*LOCAL.dniinst1.030307163043" Statement: 494e 5345 5254 2049 4e54 4f20 444e 492e INSERT INTO DNI.
444e 495f 4d57 485f 5356 544f 5520 284d DNI_MWH_SVTOU (M
5748 5f4f 555f 4e41 4d45 2c20 4d57 485f WH_OU_NAME, MWH_
574d 5149 5f4d 5347 5f49 442c 2047 4d54 WMQI_MSG_ID, GMT
5f54 4d53 544d 502c 204d 5748 5f4d 5347 _TMSTMP, MWH_MSG
5f53 5441 5455 532c 204d 5748 5f58 4d4c _STATUS, MWH_XML
5f4d 5347 2c20 4d57 485f 4d53 475f 4752 _MSG, MWH_MSG_GR
502c 204d 5748 5f42 5553 494e 4553 535f P, MWH_BUSINESS_
4752 502c 204d 5748 5f45 5854 5f4d 5347 GRP, MWH_EXT_MSG
5f49 4429 2056 414c 5545 5328 3f2c 203f _ID) VALUES(?, ?
2c20 4355 5252 454e 5420 5449 4d45 5354 , CURRENT TIMEST
414d 5020 2d20 4355 5252 454e 5420 5449 AMP - CURRENT TI
4d45 5a4f 4e45 2c20 3f2c 203f 2c20 3f2c MEZONE, ?, ?, ?,
203f 2c20 3f29 ?, ?)


2003-03-07-10.54.56.072067 Instance:dniinst1 Node:000
PID:19766(db2agent (RUNDB)) Appid:0903AA44.D42D.030307163219
global_services sqlzerdm Probe:20 Database:RUNDB

ffff 8502 ÿÿ..


2003-03-07-10.54.56.131310 Instance:dniinst1 Node:000
PID:19766(db2agent (RUNDB)) Appid:0903AA44.D42D.030307163219
global_services sqlzerdm Probe:30 Database: RUNDB

0000 0000 0000 0000 0000 0000 0000 0040 ...............@


2003-03-07-10.54.56.190141 Instance:dniinst1 Node:000
PID:19766(db2agent (RUNDB)) Appid:0903AA44.D42D.030307163219
base_sys_utilities sqleriar Probe:201 Database:RUNDB

Error tokens : 32 2


Data Title:SQLCA PID:19766 Node:000
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -911 sqlerrml: 1
sqlerrmc: 2
sqlerrp : sqlriisr
sqlerrd : (1) 0xFFFF8502 (2) 0x00000002 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) ( (9) (10) (11)
sqlstate:


Data Title:DB2RA PID:19766 Node:000
5351 4c44 4232 5241 0000 00e0 0105 0002 SQLDB2RA...à....
common_communication sqlcctcpconnr Probe:108
DIA3421W "TCPIP" protocol support: Environment Variable value
"DB2SORCVBUF" = "65536" is "accepted".

2003-03-07-10.54.55.801269 Instance:dniinst1 Node:000
PID:19766(db2agent (RUNDB)) Appid:0903AA44.D42D.030307163219
lock_manager sqlplnfd Probe:80 Database:RUNDB

Request for lock "REC: (2, 26) RID 00001A10" in mode ".NW" failed due to deadlock Application caused the lock wait is "*LOCAL.dniinst1.030307163043"
Statement: 494e 5345 5254 2049 4e54 4f20 444e 492e INSERT INTO DNI.

444e 495f 4d57 485f 5356 544f 5520 284d DNI_MWH_SVTOU (M
5748 5f4f 555f 4e41 4d45 2c20 4d57 485f WH_OU_NAME, MWH_
574d 5149 5f4d 5347 5f49 442c 2047 4d54 WMQI_MSG_ID, GMT
5f54 4d53 544d 502c 204d 5748 5f4d 5347 _TMSTMP, MWH_MSG
5f53 5441 5455 532c 204d 5748 5f58 4d4c _STATUS, MWH_XML
5f4d 5347 2c20 4d57 485f 4d53 475f 4752 _MSG, MWH_MSG_GR
502c 204d 5748 5f42 5553 494e 4553 535f P, MWH_BUSINESS_
4752 502c 204d 5748 5f45 5854 5f4d 5347 GRP, MWH_EXT_MSG
5f49 4429 2056 414c 5545 5328 3f2c 203f _ID) VALUES(?, ?
2c20 4355 5252 454e 5420 5449 4d45 5354 , CURRENT TIMEST
414d 5020 2d20 4355 5252 454e 5420 5449 AMP - CURRENT TI
4d45 5a4f 4e45 2c20 3f2c 203f 2c20 3f2c MEZONE, ?, ?, ?,
203f 2c20 3f29 ?, ?)


2003-03-07-10.54.56.426420 Instance:dniinst1 Node:000
PID:42464(db2agent (RUNDB)) Appid:0903AA44.D504.030307165146
data_protection sqlpxrbk Probe:250 Database:RUNDB
DIA1036C XA error with request type of "". Transaction was not found.

ZRC=0xFFFF8524
Dump File:/home/dniinst1/sqllib/db2dump/42464.000 Data:SQLP_DBCB
Dump File:/home/dniinst1/sqllib/db2dump/42464.000 Data:SQLP_ACB
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » unable to start a new trxn after mq backout
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.