| Author |
Message
|
| LouML |
 Posted: Fri Feb 01, 2008 11:00 am Post subject: Strange Out Of Sequence situation? |
 |
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
Is this a strange out of sequence situation or is this normal?
Sender channel CH.QM1.QM2 on the QM.QM1.01 queue manager tries to start (or gets started by command) at 12:06. There is no data in the xmit queue QM.QM2.01. An AMQ9526 is returned saying message 1 was sent but 12 was expected.
10 seconds later, the channel shows Running. A Channel Status command shows Curseqno as 0.
On QM.QM2.01, the receiver channel CH.QM1.QM2 shows Running. A Channel Status command shows Curseqno as 11.
I would expect that the sender channel would be in a Retry status until the channel was reset.
QM.QM1.01
| Code: |
bash-2.05$ echo "dis chl(CH.QM1.QM2) all" | runmqsc QM.QM1.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.QM1.01.
1 : dis chl(CH.QM1.QM2) all
AMQ8414: Display Channel details.
CHANNEL(CH.QM1.QM2) CHLTYPE(SDR)
TRPTYPE(TCP) DESCR( )
XMITQ(QM.QM2.01) MCANAME( )
MODENAME( ) TPNAME( )
BATCHSZ(50) DISCINT(6000)
SHORTRTY(10) SHORTTMR(60)
LONGRTY(999999999) LONGTMR(1200)
SCYEXIT( ) SEQWRAP(999999999)
MAXMSGL(4194304) CONVERT(NO)
SCYDATA( ) USERID( )
PASSWORD( ) MCATYPE(PROCESS)
CONNAME(111.111.111.111(1414)) HBINT(300)
BATCHINT(0) NPMSPEED(FAST)
SSLCIPH( ) BATCHHB(0)
LOCLADDR( ) KAINT(AUTO)
MCAUSER( ) ALTDATE(2007-11-25)
ALTTIME(04.47.44) SSLPEER()
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$ echo "dis chs(CH.QM1.QM2) all" | runmqsc QM.QM1.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.QM1.01.
1 : dis chs(CH.QM1.QM2) all
AMQ8417: Display Channel Status details.
CHANNEL(CH.QM1.QM2) XMITQ(QM.QM2.01)
CONNAME(111.111.111.111(1414)) CURRENT
CHLTYPE(SDR) INDOUBT(NO)
LSTSEQNO(0) LSTLUWID(0000000000000000)
CURMSGS(0) CURSEQNO(0)
CURLUWID(474944FD10037A01) STATUS(RUNNING)
LSTMSGTI(12.06.08) LSTMSGDA(2008-02-01)
MSGS(0) BYTSSENT(412)
BYTSRCVD(412) BATCHES(10)
BATCHSZ(50) HBINT(300)
NPMSPEED(FAST) CHSTATI(12.06.20)
CHSTADA(2008-02-01) BUFSSENT(11)
BUFSRCVD(11) LONGRTS(999999999)
SHORTRTS(6) JOBNAME(00002A4100000001)
MCASTAT(RUNNING) STOPREQ(NO)
LOCLADDR(222.222.222.222(37290)) SSLPEER()
RQMNAME(QM.QM2.01)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$
-------------------------------------------------------------------------------
02/01/08 12:06:10
AMQ9526: Message sequence number error for channel 'CH.QM1.QM2'.
EXPLANATION:
The local and remote queue managers do not agree on the next message sequence
number. A message with sequence number 1 has been sent when sequence number 12
was expected.
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.
----- amqrfpta.c : 334 --------------------------------------------------------
02/01/08 12:06:10
AMQ9506: Message receipt confirmation failed.
EXPLANATION:
Channel 'CH.QM1.QM2' has ended because the remote queue manager did not
accept the last batch of messages.
ACTION:
The error log for the channel at the remote site will contain an explanation of
the failure. Contact the remote Systems Administrator to resolve the problem.
----- amqrmrca.c : 670 --------------------------------------------------------
02/01/08 12:06:10
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'CH.QM1.QM2' ended abnormally.
ACTION:
Look at previous error messages for channel program 'CH.QM1.QM2' in the
error files to determine the cause of the failure.
----- amqrccca.c : 769 --------------------------------------------------------
02/01/08 12:06:20
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'CH.QM1.QM2' started.
ACTION:
None.
------------------------------------------------------------------------------- |
QM.QM2.01
| Code: |
bash-2.05$ echo "dis chl(CH.QM1.QM2) all" | runmqsc QM.QM2.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.QM2.01.
1 : dis chl(CH.QM1.QM2) all
AMQ8414: Display Channel details.
CHANNEL(CH.QM1.QM2) CHLTYPE(RCVR)
TRPTYPE(TCP) DESCR( )
BATCHSZ(50) SCYEXIT( )
SEQWRAP(999999999) MAXMSGL(4194304)
PUTAUT(DEF) SCYDATA( )
MREXIT( ) MRDATA( )
MRRTY(10) MRTMR(1000)
HBINT(300) NPMSPEED(FAST)
SSLCIPH( ) SSLCAUTH(REQUIRED)
KAINT(AUTO) MCAUSER( )
ALTDATE(2003-09-18) ALTTIME(10.11.04)
SSLPEER()
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$ echo "dis chs(CH.QM1.QM2) all" | runmqsc QM.QM2.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.QM2.01.
1 : dis chs(CH.QM1.QM2) all
AMQ8417: Display Channel Status details.
CHANNEL(CH.QM1.QM2) XMITQ( )
CONNAME(222.222.222.222) CURRENT
CHLTYPE(RCVR) INDOUBT(NO)
LSTSEQNO(11) LSTLUWID(446FF50B10000101)
CURMSGS(0) CURSEQNO(11)
CURLUWID(446FF50B10000101) STATUS(RUNNING)
LSTMSGTI( ) LSTMSGDA( )
MSGS(0) BYTSSENT(440)
BYTSRCVD(440) BATCHES(11)
BATCHSZ(50) HBINT(300)
NPMSPEED(FAST) CHSTATI(12.06.20)
CHSTADA(2008-02-01) BUFSSENT(12)
BUFSRCVD(12) LONGRTS(999999999)
SHORTRTS(10) JOBNAME(000032AB000049BD)
MCASTAT(RUNNING) STOPREQ(NO)
LOCLADDR(111.111.111.111(1414)) SSLPEER()
RQMNAME(QM.QM1.01)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$
-------------------------------------------------------------------------------
02/01/08 12:06:09
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'CH.QM1.QM2' one or more messages
could not be put to the destination queue and attempts were made to put them to
a dead-letter queue. The location of the queue is 1, where 1 is the local
dead-letter queue and 2 is the remote dead-letter queue.
ACTION:
Examine the contents of the dead-letter queue. Each message is contained in a
structure that describes why the message was put to the queue, and to where it
was originally addressed. Also look at previous error messages to see if the
attempt to put messages to a dead-letter queue failed. The program identifier
(PID) of the processing program was '1267'.
----- amqrmrca.c : 1318 -------------------------------------------------------
02/01/08 12:06:10
AMQ9526: Message sequence number error for channel 'CH.QM1.QM2'.
EXPLANATION:
The local and remote queue managers do not agree on the next message sequence
number. A message with sequence number 1 has been sent when sequence number 12
was expected.
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 : 3019 -------------------------------------------------------
02/01/08 12:06:10
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'CH.QM1.QM2' ended abnormally.
ACTION:
Look at previous error messages for channel program 'CH.QM1.QM2' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
02/01/08 12:06:20
AMQ9002: Channel 'CH.QM1.QM2' is starting.
EXPLANATION:
Channel 'CH.QM1.QM2' is starting.
ACTION:
None. |
|
|
| Back to top |
|
 |
| ashu |
| Posted: Sat Feb 02, 2008 3:32 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
|
| Back to top |
|
|
| LouML |
| Posted: Thu Feb 07, 2008 12:01 pm Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
I know how to Reset a Channel Sequence Number.
However, I thought that if there were an out of sequence situation, the channel would not start. In my situation, the channel starts. The seqeunce numbers look out of sync. Then the channel stops when it properly times out. Then the next time it starts, the same thing happens. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 07, 2008 2:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You mean to say that your channel does not go into retry status???
A channel in retry status may or may not be healthy... It all depends on the reason for the retry. It the reason is because the TCP route is momentarily unavailable this is a healthy status.
If it is because there is a sequence # problem this is a situation that demands fixing (probably ASAP)
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ashu |
| Posted: Sat Feb 09, 2008 12:50 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
| LouML wrote: |
I know how to Reset a Channel Sequence Number.
However, I thought that if there were an out of sequence situation, the channel would not start. In my situation, the channel starts. The seqeunce numbers look out of sync. Then the channel stops when it properly times out. Then the next time it starts, the same thing happens. |
AFAIK the channel start does not depend on the message sequence number. The message sequence number is set to 1 by default but can be altered manually and the sending and receiving ends can agree upon a new initial sequence number. Due to this reason it is very difficult for the channel to predict the value that will be set manually and hence the MCA doesn't care about the seqnum but rather sees whether the objects that are going to play a part in the whole intercommunication are well defined or not. Please correct me if I am wrong. 
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Feb 09, 2008 11:59 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You are wrong. If sequence numbers didn't matter there would be no reason for them. The sending and receiving sides' sequence #s must match. If they don't, then the channel should not start, it should go retrying, and both sides' error logs should report a sequence # error.
LouML has a legitimate question.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ashu |
| Posted: Sun Feb 10, 2008 10:05 pm Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
| PeterPotkay wrote: |
You are wrong. If sequence numbers didn't matter there would be no reason for them. The sending and receiving sides' sequence #s must match. If they don't, then the channel should not start, it should go retrying, and both sides' error logs should report a sequence # error.
LouML has a legitimate question. |
 I am sorry for the incorrect information...but I seriously thought that the seq # was for the applications to keep track of their messages...I take back my words...I hope to get some insight through this discussion myself...
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 11, 2008 1:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ashu wrote: |
| I seriously thought that the seq # was for the applications to keep track of their messages |
Channel sequence numbers are generally invisible to applications.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| UglyAngelX |
| Posted: Mon Feb 11, 2008 8:53 am Post subject: |
|
|
Voyager
Joined: 04 Dec 2001
Posts: 90
Location: BEARS FAN IN STEELER COUNTRY
|
| I ran into this issue and it kept popping up, over and over. The way we resolved the issue was to delete and recreate the channel. |
|
| Back to top |
|
|
| LouML |
| Posted: Mon Feb 11, 2008 9:09 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
Sorry for the delayed reply. I was out of the office on Friday.
I reset the sender channel and the messages stopped coming up.
Of course, this does not explain why the channel would run after reporting the sequence number error.
To fjp_saper
- correct, the channel would report the error but go to Running status, not Retrying status. A Channel Status display from both channels (sdr and rcvr) would show different seq#s.
I guess I'll keep a close eye on it and see if the problem returns. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Feb 11, 2008 4:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| LouML wrote: |
Sorry for the delayed reply. I was out of the office on Friday.
I reset the sender channel and the messages stopped coming up.
Of course, this does not explain why the channel would run after reporting the sequence number error.
To fjp_saper
- correct, the channel would report the error but go to Running status, not Retrying status. A Channel Status display from both channels (sdr and rcvr) would show different seq#s.
I guess I'll keep a close eye on it and see if the problem returns. |
There was a problem reported that had to do with setting the number seq and an authorization on the channel for the user setting the seqnum?? Check if you need the APAR...(my memory is slowly going away) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Feb 11, 2008 8:34 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| fjb_saper wrote: |
| There was a problem reported that had to do with setting the number seq and an authorization on the channel for the user setting the seqnum?? Check if you need the APAR...(my memory is slowly going away) |
That was a problem we talked about here a couple months back. A bug in 6.0.2.1. But in that case the channel would not start because the bug was preventing the seq #s from sticking on a reset.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
