| Author |
Message
|
| ishimi22 |
 Posted: Tue Dec 09, 2008 6:31 pm Post subject: Message receipt confirmation failed |
 |
|
Newbie
Joined: 09 Dec 2008
Posts: 2
|
Hello,
I'm new in this field, really need some help and explaination regarding this error.
Error at MB
----- amqrfpta.c : 340 --------------------------------------------------------
11/28/08 05:42:38 - Process(2531464.1) User(mqm) Program(runmqchl_nd)AMQ9506: Message receipt confirmation failed.
EXPLANATION:
Channel 'QMPK1.QMPG1' has ended because the remote queue manager did not accept the last batch of messages.
Error at MQ
ACTION:
None.
11/28/08 05:48:38 - Process(454772.6904064) User(mqm) Program(amqrmppa)AMQ9526: Message sequence number error for channel 'QMPK1.QMPG1'.
EXPLANATION:
The local and remote queue managers do not agree on the next message sequencenumber. A message with sequence number 158509 has been sent when sequence
number 149343 was expected.
ACTION:
Determine the cause of the inconsistency. It could be that the synchronizationinformation has become damaged, or has been backed out to a previous version.
If the situation cannot be resolved, the sequence number can be manually resetat the sending end of the channel using the RESET CHANNEL command.
Why did the sequence number error happend? |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Dec 10, 2008 12:34 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Sunspot activity? Chaos effect?
With so little information there is little chance of helping you. Read the Intercommunication manual, check logs etc. on both queue managers, check what 'work' has been carried out on the server(s).
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 10, 2008 12:55 am Post subject: Re: Message receipt confirmation failed |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ishimi22 wrote: |
| Why did the sequence number error happend? |
Given the large discrepancy in numbers, one possible explaination is that the receiving queue manager was restored from an old backup.
Other explainations are possible, and indeed likely. Most of them involve an under-qualified human meddling, either in WMQ or the network.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ishimi22 |
| Posted: Sun Dec 14, 2008 7:30 pm Post subject: |
|
|
Newbie
Joined: 09 Dec 2008
Posts: 2
|
I see.. Is it possible this sequence error happend b'coz of stopping the channel? If possible, isn't the message supposed to get in queue until the channel started back? [confiused  ] |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Dec 14, 2008 7:47 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ishimi22 wrote: |
| I see.. Is it possible this sequence error happend b'coz of stopping the channel? If possible, isn't the message supposed to get in queue until the channel started back? [confiused ] |
No stopping and starting the channels does not mess with sequence numbers. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 15, 2008 12:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ishimi22 wrote: |
| I see.. Is it possible this sequence error happend b'coz of stopping the channel? |
No.
| ishimi22 wrote: |
| Isn't the message supposed to get in queue until the channel started back? [confiused ] |
Yes. Also in the event of a "predictable" error (e.g. network failure) the 2 MCA will re-handshake and re-negociate sequence numbers. So something exceptional has to happen to get a sequence number error. Something very expectional to get such a large one where neither number is 1 or 0.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
