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 » WebSphere Message Broker (ACE) Support » MQCC=1, MQRC=2003:Unable to commit a WebSphere MQ transactio

Post new topic  Reply to topic
 MQCC=1, MQRC=2003:Unable to commit a WebSphere MQ transactio « View previous topic :: View next topic » 
Author Message
bokachod
PostPosted: Thu Apr 30, 2009 6:21 am    Post subject: MQCC=1, MQRC=2003:Unable to commit a WebSphere MQ transactio Reply with quote

Newbie

Joined: 30 Apr 2009
Posts: 6

Hi,

I have msgflow MQ I/p Node -->Compute node (DB Update/Create)---> MQ o/p Node(AQ(alias queue)-->RQ(remote queue)-->trg Q).

AQ,RQ is on queue Manager QM1 and trg Q is on queue manager QM2.

Ctach and failure terminal of MQ i/p Node is connected to fail Q.

Issue:--Sometime it happens that msg is getting backed out to the backout queue. with error as
Unable to commit a WebSphere MQ transaction; MQCMIT failed; queue manager=QM1, MQCC=1, MQRC=2003.
(this error message is taken from syslog)

this is happen once in a week or you can say for every 1 million message that is being processed.

I also look into the other post in MQ series for same error.

But I did not understand the exact issue.

Can anybody help me out with this issue with good explanation.

THANKS A LOT FOR YOUR TIME!!!
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Apr 30, 2009 6:56 am    Post subject: Re: MQCC=1, MQRC=2003:Unable to commit a WebSphere MQ transa Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

bokachod wrote:
Can anybody help me out with this issue with good explanation.


What does the broker (rather than the queue manager) log have to say?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
bokachod
PostPosted: Thu Apr 30, 2009 11:35 am    Post subject: Reply with quote

Newbie

Joined: 30 Apr 2009
Posts: 6

Hi Victor,

this is what system log has to say :---

WebSphere Broker v6007[25224]: (brkName.eg)[1610406832]BIP2643W: Unable to commit a WebSphere MQ transaction; MQCMIT failed; queue manager=QM1, MQCC=1, MQRC=2003. : brkName.aecd2bb9-1f01-0000-0080-9aeaa62427cc: /build/S600_P/src/DataFlowEngine/ImbMqManager.cpp: 2310: ImbMqConnection::commitCurrentTransaction: ComIbmMQConnectionManager: ComIbmMQConnectionManager
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Apr 30, 2009 8:21 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

1 minute with the infocenter reason code list would have given you this:
Quote:
2003 (X'07D3') MQRC_BACKED_OUT
Explanation:

The current unit of work encountered a fatal error or was backed out. This occurs in the following cases:

* On an MQCMIT or MQDISC call, when the commit operation has failed and the unit of work has been backed out. All resources that participated in the unit of work have been returned to their state at the start of the unit of work. The MQCMIT or MQDISC call completes with MQCC_WARNING in this case.
o On z/OS, this reason code occurs only for batch applications.
* On an MQGET, MQPUT, or MQPUT1 call that is operating within a unit of work, when the unit of work has already encountered an error that prevents the unit of work being committed (for example, when the log space is exhausted). The application must issue the appropriate call to back out the unit of work. (For a unit of work coordinated by the queue manager, this call is the MQBACK call, although the MQCMIT call has the same effect in these circumstances.) The MQGET, MQPUT, or MQPUT1 call completes with MQCC_FAILED in this case.
o On z/OS, this case does not occur.

Completion Code:

MQCC_WARNING or MQCC_FAILED
Programmer Response:

Check the returns from previous calls to the queue manager. For example, a previous MQPUT call may have failed.

This seems pretty straight forward to me. Which part of it did you not understand?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
bokachod
PostPosted: Fri May 01, 2009 4:13 am    Post subject: Reply with quote

Newbie

Joined: 30 Apr 2009
Posts: 6

Hi,

I am ok with the explanation , that the resource taking part in the a given unit of work is exhausted. But how do I found that for which resource it is happening...... syslog doesn't have entry, neither mqm has any error.

that's y I written to provode good explanation.?

Thanks
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri May 01, 2009 4:32 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

bokachod wrote:
how do I found that for which resource it is happening...... syslog doesn't have entry, neither mqm has any error.


It's the queue manager log that's full. Syslog won't have an entry because it doesn't (generally) record application events, and mqm won't log an error because it's successfully returned a reason code.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
JosephGramig
PostPosted: Fri May 01, 2009 9:06 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

Please post your qm.ini file.
Back to top
View user's profile Send private message AIM Address
shyamkumarsharma001
PostPosted: Mon Jun 22, 2015 11:57 pm    Post subject: Reply with quote

Novice

Joined: 24 May 2011
Posts: 18

Hi,

Can this happen even if the MQInput transaction mode is set to "No" rather than "Yes" which makes the flow non-transactional?
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 » WebSphere Message Broker (ACE) Support » MQCC=1, MQRC=2003:Unable to commit a WebSphere MQ transactio
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.