| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQCMT fails with MQRC 2003 (MQRC_BACKED_OUT) |
« View previous topic :: View next topic » |
| Author |
Message
|
| Lisssenok |
 Posted: Mon Oct 13, 2008 11:57 pm Post subject: MQCMT fails with MQRC 2003 (MQRC_BACKED_OUT) |
 |
|
Newbie
Joined: 13 Oct 2008
Posts: 4
|
Hi 2 all, i have such a problem:
MQS on AIX 5.3, during backup qmanager doesn't answer HTTP-Requests from applicationes, the flow stops, one needs to start it again.
I have 3 questiones:
-- what happens in this moment with messages in queue.
-- how I can fix problem with flow.
-- why qmanager doesn't answere requests.
P.S. Solving this problem from IBM Support cannot be used, I haven't technical possibilities for that. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Oct 14, 2008 12:30 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Reason Code 2003 x'7D3'
MQRC_BACKED_OUT
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
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.
Corrective action: Check the returns from previous calls to the queue manager. For example, a previous MQPUT call may have failed.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Lisssenok |
| Posted: Tue Oct 14, 2008 2:56 am Post subject: |
|
|
Newbie
Joined: 13 Oct 2008
Posts: 4
|
|
| Back to top |
|
|
| Lisssenok |
| Posted: Tue Oct 14, 2008 10:41 pm Post subject: |
|
|
Newbie
Joined: 13 Oct 2008
Posts: 4
|
Yeah, MQPUT have really failed:
>Unable to write message to queue
> 'T_FLEXPD_NMS.CONFIGURATION.REPLY' on queue manager 'W2MA05'. MQPUT
> failed: MQCC=2; MQRC=2003;
but i don't know, what I must do with this 
and this error (below) repeats often:
user:err|error MQSIv500[2273574]:
> (W2MA05.T_NMS)[8739]BIP2232E: Error detected whilst handling a
> previous error in node |
|
| Back to top |
|
|
| David.Partridge |
| Posted: Tue Oct 14, 2008 11:02 pm Post subject: |
|
|
Master
Joined: 28 Jun 2001
Posts: 249
|
Are you by any chance putting LOTS of messages and not issuing a commit?
That could explain the MQRC_BACKED_OUT error that you are seeing.
_________________
Cheers,
David C. Partridge |
|
| Back to top |
|
|
| Lisssenok |
| Posted: Tue Oct 14, 2008 11:44 pm Post subject: |
|
|
Newbie
Joined: 13 Oct 2008
Posts: 4
|
All processes run normally to 1.10 AM, next backup process runs, next loading rises, next all replies are NMSAdapterExceptions, they show error messages, that NMS isn't arrived, next replies disappear , flow stops.
It must be restarted manually each time. |
|
| 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
|
|
|
|
