Hi Folks,
We use a HA clustered system across 2 machines M1 & M2 in Solaris. We were at MQSI CSD Level 2 and WMQ 5.3 CSD 6. Yesterday, we upgraded our MQSI to MQSI CSD 6. We tested using msgs that should fail for parsing, reformatting etc. But the msg did not fail, it kept retrying with the following errors: Jul 29 11:06:42 weut2 MQSeries: [ID 702911 user.error] (QM1.UAT.5CD)[14]BIP2607E : Unable to rollback an MQSeries transaction; MQBACK failed; queue manager ='QM1.UAT ', MQCC=2, MQRC=2195; message flow node 'ComIbmMQConnectionManager'. : QM1.UAT.ad00 6e44-f000-0000-0080-8a7e099e611d: /build/S210_P/src/DataFlowEngine/ImbMqManager.cpp: 789: ImbMqManag er::threadCleanupInner: ComIbmMQConnectionManager: ComIbmMQConnectionManager Jul 29 11:06:42 weut2 MQSeries: [ID 702911 user.error] (QM1.UAT.5CD)[14]BIP2607E : Unable to rollback an MQSeries transaction; MQBACK failed; queue manager ='QM1.UAT ', MQCC=2, MQRC=2195; message flow node 'ComIbmMQConnectionManager'. : QM1.UAT.ad00 6e44-f000-0000-0080-8a7e099e611d: /build/S210_P/src/DataFlowEngine/ImbMqManager.cpp: 789: ImbMqManag er::threadCleanupInner: ComIbmMQConnectionManager: ComIbmMQConnectionManager Also MQ Error logs show: AMQ7605: The XA resource manager DB2 XSDSN has returned an unexpected return code -6, when called for xa_rollback. EXPLANATION: WebSphere MQ received an unexpected return code when calling XA resource manager DB2 XSDSN at its xa_rollback entry point. This indicates an internal error, either within MQ or the resource manager. ACTION: Try to determine the source of the error. A trace of the failure could be used to look at the XA flows between MQ and the resource manager. MQ has allocated an RMId of 3 to this resource manager. This will be useful when isolating the flows associated with the resource manager concerned. If the error occurs on an xa_commit or xa_rollback request, the queue manager will not attempt to redeliver the commit or rollback instruction for this transaction, until after the queue manager has been restarted. The transaction indoubt is identified by the following XID of X'004D514D0000002000000004410818F52000772D4E5943474358325F47435357455554325F514D312E55415400000001'. If you think that the error lies within the queue manager, contact your IBM support center. Do not discard any information describing the problem until after the problem has been resolved. Following this I thought it's a recurrence of IBM PMR IC30970: GLOBALLY CO-ORDINATED FLOW INVOKING NEON PARSER CAUSE XA PROBLEMLEAVING DB INVOLVED IN A TRANSACTION LOCKOUT. Accordingly there is a recommendation to set the envt parameter MQSI_NEON_XA_ON to anything. Accordingly, I set the envt variable in MQSI user .profile as export MQSI_NEON_XA_ON=yes But still it gave me the same MQ begin errors on testng the parsing failure msgs. Has anyone else experienced this? Any pointers would be highly appreciated. Thanks in Advance. - Bharath
This e-Mail may contain proprietary and confidential information and is sent for the intended recipient(s) only. If by an addressing or transmission error this mail has been misdirected to you, you are requested to delete this mail immediately. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or its attachment other than by its intended recipient/s is strictly prohibited. Visit Us at http://www.polaris.co.in
