| Author |
Message
|
| pan21 |
 Posted: Tue Sep 23, 2014 11:06 pm Post subject: AMQ9526 channel sequnce num error |
 |
|
Newbie
Joined: 23 Sep 2014
Posts: 3
|
Halo
I neeed small help on channel sequence number issue... i dont know the sender channel i now reciver channel only
A message with sequence number 231863 has been sent when sequence
number 231837 was expected.
i have reset the channel on reciver side using reset channel(xxx) seqnum(231837)
its not wokring again error message in error log how to solve this problem from reciver side
09/24/2014 07:12:26 AM - Process(14480.17860) User(mqm) Program(amqrmppa)
Host(sl007) Installation(Installation1)
VRMF(7.5.0.3) QMgr(MQ1)
AMQ9526: Message sequence number error for channel 'S1'.
EXPLANATION:
The local and remote queue managers do not agree on the next message sequence
number. A message with sequence number 231863 has been sent when sequence
number 231837 was expected. The remote host is '212.14.64.8'.
ACTION:
Determine the cause of the inconsistency. It could be that the synchronization
information has become damaged, or has been backed out to a previous version.
If the situation cannot be resolved, the sequence number can be manually reset
at the sending end of the channel using the RESET CHANNEL command.
----- amqrmtra.c : 4269 -------------------------------------------------------
09/24/2014 07:12:26 AM - Process(14480.17860) User(mqm) Program(amqrmppa)
Host(sl007) Installation(Installation1)
VRMF(7.5.0.3) QMgr(MQ1)
AMQ9999: Channel's1' to host '212.149.64.58 (212.149.64.5 '
ended abnormally.
EXPLANATION:
The channel program running under process ID 14480 for channel
's1' ended abnormally. The host name is '212.149.64.58
(212.149.64.5'; in some cases the host name cannot be determined and so is
shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide. |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Wed Sep 24, 2014 1:57 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Shouldn't you be resetting the channel to the number that is sent rather than what is expected?. ie. try the command
| Code: |
reset channel(xxx) seqnum(231863)
|
That way the number sent will match what is expected.
However, RESET CHL should not normally be necessary. Only do this if you are fairly confident you know what has 'gone wrong'. Since you do risk duplicating messages etc.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| pan21 |
| Posted: Wed Sep 24, 2014 2:22 am Post subject: Thank You for the information |
|
|
Newbie
Joined: 23 Sep 2014
Posts: 3
|
we have contacted the sender responsble persone we informed them they have done reset on sender side ..
we have no idea on resteing the channel on reciver using you comment ... dontn know what happen after i done on reciver 
thnak you paul |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 24, 2014 5:21 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| PaulClarke wrote: |
Shouldn't you be resetting the channel to the number that is sent rather than what is expected?. ie. try the command
| Code: |
reset channel(xxx) seqnum(231863)
|
That way the number sent will match what is expected.
However, RESET CHL should not normally be necessary. Only do this if you are fairly confident you know what has 'gone wrong'. Since you do risk duplicating messages etc.
Cheers,
Paul. |
For clarity, MQ does not, and will not lose or duplicate messages; but your applications might do so.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Wed Sep 24, 2014 6:18 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
How sweet..........are you telling me how MQ and Channels work ?
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| pan21 |
| Posted: Wed Sep 24, 2014 7:17 am Post subject: I am New to MQ admin |
|
|
Newbie
Joined: 23 Sep 2014
Posts: 3
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 24, 2014 8:10 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| PaulClarke wrote: |
| How sweet..........are you telling me how MQ and Channels work ? |
No offense intended. I'm always open to learning new stuff.
How does (re)setting the seqwrap value result in a duplicate message?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Wed Sep 24, 2014 8:57 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
No offence caused I was just mildly amused that you saw fit to correct the person who wrote the MQ channel code.
When a sender and receiver channel communicate they store their state in a persisted store, either a scratchpad or an MQ Q depending on platform/version. In other words this data remembers where the channel got up to. Now, normally the state data at the two ends match. When a channel comes up it can determine whether the last batch or messages was sent or not and recover any indoubts.
However, if something out-of-line has happened then you could get a sequence number error. For example, suppose you deleted and redefined your channel or you restored your state from a back-up log. Or suppose you are directing your channel to a different Queue Manager now. Or, heaven forbid, there's a bug in the MQ code. Or, as can happen, the log is stored on a data device which lies about it's write-through-cache. All of these things can cause a sequence number failure.
A sequence number failure is nothing more than the channel telling you that the two ends of the channel don't agree on the state of the messages and that something odd has happened. It is up to you, the user, to determine whether that 'something' is understood and of no concern or whether you might have a real issue.
As for duplicating messages. Suppose a channel sends a batch of messages and requests confirmation and then there's a network failure. The channel is indoubt but the receiver channel has processed the batch. However, let's now suppose that one of the errors above happens. The channel comes back up, says 'did you receive batch xyz' and is told 'no'. The sender channel will now resend that batch of messages which will duplicate them all.
A sequence number failure can be nothing more serious than someone has deleted and redefined a channel or you are sending to an alternate Queue Manager. However, it can indicate something more serious and you are always recommended to understand why you are getting one.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Wed Sep 24, 2014 9:01 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
| Quote: |
| How does (re)setting the seqwrap value result in a duplicate message? |
Actually I should probably also state that resetting the channel with a RESET CHANNEL command has nothing to do with the sequence wrap value. RESET CHANNEL merely tells the channel what sequence number to send/expect (depending on channel type) the next time it starts.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 24, 2014 9:57 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Thank you, Paul, for your detailed explanation. I yield.
My clients have come to depend on MQ's no loss/no duplication for normal operation, including recovery from some "usual" hardware/software failures.
When I sell this concept, I do offer "...except in some highly unusual circumstances" where sysadmins can adversely affect no loss/no duplication. I do not begin the sales pitch with "MQ might lose messages if...".
Again, thanks.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
