| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message receipt confirmation failed error on cluster sender |
« View previous topic :: View next topic » |
| Author |
Message
|
| Anirud |
 Posted: Wed Sep 13, 2006 10:46 am Post subject: Message receipt confirmation failed error on cluster sender |
 |
|
Master
Joined: 12 Feb 2004
Posts: 285
Location: Vermont
|
Howdy,
Here is the scenarion:
Sending QMgr: QMSEND (HP-UX) -- MQ 5.3.0.12
Receiving QMgr: QMRECV (z/OS)
Cluster queue: TEST.X
/var/mqm/log/QMGR1 was full and that brought the QMgr down. 73000 + messages were on the Cluster Transmit Queue these messages were destined to TEST.X queue which is QMRECV). We added some disk space and started the QMgr (QMSEND). The MQ log FS was filling up. So, cleared all the messages from the SYSTEM.CLUSTER.TRANSMIT.QUEUE. Checked error logs and found message receipt confirmation failed errors written to the error logs. So, did a reset on the cluster sender channel (TO.QMRECV) and started the channel. Channel started successfully. Messages were flowing to other queues (TEST.A, TEST.B etc) on the Mainframe QMgr (QMRECV).
But, if we write messages to the TEST.X queue, the cluster sender (TO.QMRECV) goes to retrying state. I did a refresh cluster on the QMSEND and found that the channel was indoubt. I ran the resolve channel command (resolve chl(to.qmrecv) action(commit) ). Started channel successfully. Again, if I write message to TEST.X queue, the cluster sender goes to retrying state and the same error is written to the error logs (message receipt confirmation failed).
Any idea? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Sep 13, 2006 4:20 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Could it be authentication? Is the sender Id defined to the receiver qmgr?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bbeardsley |
| Posted: Thu Sep 14, 2006 5:40 am Post subject: |
|
|
Acolyte
Joined: 17 Dec 2001
Posts: 52
Location: Dallas, TX, USA
|
| What is the depth of TEST.X queue? |
|
| Back to top |
|
|
| Anirud |
| Posted: Mon Sep 18, 2006 2:52 pm Post subject: |
|
|
Master
Joined: 12 Feb 2004
Posts: 285
Location: Vermont
|
Sorry guys,
I was pretty much occupied with other stuff (sorry for the late response).
This is what I found. On the Mainframe QMgr (QMRECV), errors were written to the logs saying that "the QMgr was not able to put message to the queue as the message expired". Messages were persistent messages. I think the expiry was very low and as a result, the message expired even before the QMgr was able to write the message to the Queue.
I asked the testing team to increase the expiry time. I recycled QMSEND and did a refresh cluster repos(yes) and didn't happen to see the issue again. All good, as of now.
I am with the assumption that the QMgr was responsible to deliver the persistent message and as it did not find the message (message expired) to deliver to the destination queue, the cluster sender channel went to indoubt state.
Am I right? |
|
| 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
|
|
|
|
