| Author |
Message
|
| mikeHT |
 Posted: Fri Mar 17, 2006 2:32 pm Post subject: Messages stuck in SYSTEM.CLUSTER.TRANSMIT.QUEUE and refuse |
 |
|
Voyager
Joined: 01 Jul 2005
Posts: 82
|
Hi MQ cluster experts:
I have a working MQ cluster but there are instances that messages are stuck in SYSTEM.CLUSTER.TRANSMIT.QUEUE refuse to go to the target q. The messages are destined to a Localqueue on QMGR (full repos). Application puts the messages via a clustered qa which is targetting the localqueue. cluster qa & localqueue are all put enabled and the environment works. The maxmsgl on SYSTEM.CLUSTER.TRANSMIT.QUEUE & targetq is set to high enough so that there is no limitation of the message sizes which are put to the clustered qa & target queue. I opened case with IBM, did the clussdr stop/resolve/commit/reset. we can't figure out why messages are stuck in the transmit queue. Used the qload to save msg to file, clear locks to the transmit queue and put them back to the transmit queue, the msg still refuse to go.
I checked that the MQ cluster is working by
amqsput cluster-qa LocalQMGR.
Anyone could help? Thank you in advance. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Mar 17, 2006 3:41 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Have you determined if the RQMName on the messages is a valid name?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mikeHT |
| Posted: Fri Mar 17, 2006 5:47 pm Post subject: |
|
|
Voyager
Joined: 01 Jul 2005
Posts: 82
|
I used q.exe to browse one message and got the message descriptor below. I cut off the data portion though. There is RQMGRName to be seen. But it has been work like that for other MQ cluster environments.
============================================================================
Message Descriptor (MQMD)
StrucId :'MD '
Version :1
Report :0
Message Type :8
Expiry :-1
Feedback :0
MQEncoding :0x'222'
CCSID :437
Format :'MQXMIT '
Priority :0
Persistence :1 (Persistent)
Message Id :A M Q LocalQMGR
R ? D 414D51204352444130322020202020200A5218442000016A
Correl. Id :T O . R E M O T E Q M G R
544F2E4E5347413031202020202020202020202020202020
Backout Cnt. :0
ReplyToQ :' '
ReplyToQMgr :'LocalQMGR '
UserId :'SYSTEM '
AccountingTkn:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
0100000000000000000000000000000000000000000000000000000000000000
ApplIndentity:' '
PutApplType :7
PutApplName :'LocalQMGR '
Put Date :'20060315'
Put Time :'20555840'
ApplOriginDat:' '
XQH ?
CLUSTER.QANAME
MD ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Mar 18, 2006 6:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Can you post the same gathered with amqsbcg rather than q.exe? You can strip off the data portion, but make sure that you leave everything before the first character of your data.
We probably need to see the full transmission header as byte values.
The only real reason messages get stuck on the cluster transmission queue is because they have been addressed to a queue manager that is not available in the cluster. The issue now becomes figuring out which qmgr they are addressed to, and why the cluster doesn't think that qmgr is available.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Mar 18, 2006 8:16 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
and display the channel statuses on the QM where the message is stuck. I want to see if any of the channels to the QM you think this message should go to are retrying, or binding, or stopped, or......
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mikeHT |
| Posted: Sat Mar 18, 2006 8:21 am Post subject: |
|
|
Voyager
Joined: 01 Jul 2005
Posts: 82
|
AMQSBCG0 - starts here
**********************
MQOPEN - 'SYSTEM.CLUSTER.TRANSMIT.QUEUE'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 437
Format : 'MQXMIT '
Priority : 0 Persistence : 1
MsgId : X'414D5120435244413032202020202020D2301B4420008E02'
CorrelId : X'544F2E4E5347413031202020202020202020202020202020'
BackoutCount : 1
ReplyToQ : ' '
ReplyToQMgr : 'LocalQMGR '
** Identity Context
UserIdentifier : 'SYSTEM '
AccountingToken :
X'0100000000000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '7'
PutApplName : 'LocalQMGR '
PutDate : '20060318' PutTime : '13502012'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 943 bytes
00000000: 5851 4820 0100 0000 4E53 472E 524F 5554 'XQH ....CLUST.QA'
00000010: 4552 2020 2020 2020 2020 2020 2020 2020 ' '
dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
57 : dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
AMQ8409: Display Queue details.
DESCR(WebSphere MQ Cluster Transmission Queue)
PROCESS( ) BOQNAME( )
INITQ( ) TRIGDATA( )
CLUSTER( ) CLUSNL( )
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) CRDATE(2006-03-16)
CRTIME(08.27.52) ALTDATE(2006-03-1
ALTTIME(11.03.4 GET(ENABLED)
PUT(ENABLED) DEFPRTY(0)
DEFPSIST(NO) MAXDEPTH(999999999)
MAXMSGL(100000000) BOTHRESH(0)
SHARE DEFSOPT(SHARED)
HARDENBO MSGDLVSQ(PRIORITY)
RETINTVL(999999999) USAGE(XMITQ)
TRIGGER TRIGTYPE(FIRST)
TRIGDPTH(1) TRIGMPRI(0)
QDEPTHHI(80) QDEPTHLO(20)
QDPMAXEV(ENABLED) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QSVCINT(999999999)
QSVCIEV(NONE) DISTL(YES)
NPMCLASS(NORMAL) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(2)
OPPROCS(10) CURDEPTH(27)
I'm concerned about the high OPPROCS count:10. doing the dis qs(name) type(handle) all, I can see 8 other PIDs having some type of handle on the transmit queue and only way to get the PIDs to release handle is issue taskkill (qmgr is on win2003). The other 2 PIDs are for
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(8924)
APPLTAG(ebSphere MQ\bin\AMQRMPPA.EXE) TID(156)
APPLTYPE(SYSTEM) CHANNEL(TO.QMGRFULL-REPOS)
CONNAME(10.3.231.16) BROWSE(YES)
INPUT(SHARED) INQUIRE(YES)
OUTPUT(YES) SET(YES)
USERID(MUSR_MQADMIN@win2003server)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(6284)
APPLTAG(ebSphere MQ\bin\amqrrmfa.exe) TID(1)
APPLTYPE(SYSTEM) CHANNEL()
CONNAME() BROWSE(YES)
INPUT(SHARED) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(MUSR_MQADMIN@win2003server)
Example of application handle on the transmit queue:
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(20252)
APPLTAG(appl1.exe) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(20252)
APPLTAG(appl1.exe) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 18, 2006 9:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
What about that channel status though ?
dis chs(to.*) assuming that your cluster receiver/senders are named to.xxx. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mikeHT |
| Posted: Sat Mar 18, 2006 10:13 am Post subject: |
|
|
Voyager
Joined: 01 Jul 2005
Posts: 82
|
dis chs(*)
62 : dis chs(*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.QMGR-Full-Repos) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(192.168.231.16(1414)) CURRENT
CHLTYPE(CLUSSDR) STATUS(RUNNING)
RQMNAME(QMGR-Full-Repos)
dis chs(TO.LocalQMGR)
66 : dis chs(TO.LocalQMGR)
AMQ8420: Channel Status not found.
dis qs(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
67 : dis qs(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) IPPROCS(2)
OPPROCS(10) CURDEPTH(27)
UNCOM(YES)
refresh cluster(CNAME)
Tail of AMQERR01.LOG
-------------------------------------------------------------------------------
3/18/2006 11:16:05
AMQ9001: Channel 'TO.LocalQMGR' ended normally.
EXPLANATION:
Channel 'TO.LocalQMGR' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
3/18/2006 13:08:02
AMQ9420: No repositories for cluster CNAME.
EXPLANATION:
The queue manager has received information about a cluster for which no
repositories are known.
ACTION:
Alter the REPOS or REPOSNL attribute of the queue manager, that is to have a
full repository for the cluster, to specify the cluster name.
-------------------------------------------------------------------------------
3/18/2006 13:08:02
AMQ9442: Refresh Cluster command processed.
EXPLANATION:
The Refresh Cluster(CNAME) command caused 11 objects to be refreshed and 1
objects to be republished.
ACTION:
None.
-------------------------------------------------------------------------------
I'm thinking that the partial repos LocalQMGR can communicate with Full-Repos qmgr because of the msgs stuck in the cluster.transmit.queue.
Manually, I fixed the cluster by clearing SYSTEM.CLUSTER.TRANSMIT.QUEUE (after backingup msgs) and everything starting going fine again. I can put the backedup msg to TRANSMIT.QUEUE again and msgs would sometimes go and sometimes won't go. |
|
| Back to top |
|
|
| mikeHT |
| Posted: Sat Mar 18, 2006 10:49 am Post subject: |
|
|
Voyager
Joined: 01 Jul 2005
Posts: 82
|
I cleared handles from the TRANSMIT.QUEUE and backedup/cleared msg from TRANSMIT.QUEUE. Cluster is back to running again:
dis chs(*)
5 : dis chs(*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.QMGR-Full-Repos) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(192.168.231.16(1414)) CURRENT
CHLTYPE(CLUSSDR) STATUS(RUNNING)
RQMNAME(QMGR-Full-Repos)
AMQ8417: Display Channel Status details.
CHANNEL(TO.LocalQmgr) XMITQ( )
CONNAME(192.168.231.16) CURRENT
CHLTYPE(CLUSRCVR) STATUS(RUNNING)
RQMNAME(QMGR-Full-Repos)
I used qload to put the 36 msg to the TRANSMIT.QUEUE and they did not go to the QMGR-Full-repos yet
dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE) curdepth
7 : dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE) curdepth
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) CURDEPTH(0)
dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE) curdepth
8 : dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE) curdepth
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) CURDEPTH(35)
dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE) curdepth
9 : dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE) curdepth
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) CURDEPTH(35)
Anything I need to alter on the TRANSMIT.QUEUE properties? Thank you. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Mar 18, 2006 12:13 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That can't be the full transmission queue header.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| EddieA |
| Posted: Sat Mar 18, 2006 1:59 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Well, the 1st post has:
| Quote: |
| Correl. Id :T O . R E M O T E Q M G R |
But none of the information you have given us so far points to you having a Channel/QM that matches.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Mar 18, 2006 2:11 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
| mikeHT wrote: |
I used qload to put the 36 msg to the TRANSMIT.QUEUE and they did not go to the QMGR-Full-repos yet
|
wha??? Are you opening and putting messages directly into "SYSTEM.CLUSTER.TRANSMIT.QUEUE"?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Sat Mar 18, 2006 2:26 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
| I used qload to put the 36 msg to the TRANSMIT.QUEUE and they did not go to the QMGR-Full-repos yet |
 Yikes! |
|
| Back to top |
|
|
| mikeHT |
| Posted: Sat Mar 18, 2006 5:30 pm Post subject: |
|
|
Voyager
Joined: 01 Jul 2005
Posts: 82
|
jefflowrey
grand master
Posted: Sat Mar 18, 2006 3:13 pm Post subject:
--------------------------------------------------------------------------------
That can't be the full transmission queue header.
________________
"grand master" just means "posts too much"
HI Jefflowrey:
I swear that is what I got from the amqsbcg, but that is only the first message which I copied and pasted (with edits to the info for LocalQmgr, remoteqmgr names). Is there another tool which allows me to get the full transmission header? Thanks
--------------------------------------------------------------------------------
Well, the 1st post has:
Quote:
Correl. Id :T O . R E M O T E Q M G R
But none of the information you have given us so far points to you having a Channel/QM that matches.
Cheers,
_________________
Eddie Atherton
IBM Certified Specialist - MQSeries and WebSphere MQ Integrator
IBM Certified Developer - MQSeries
IBM Certified Solutions Expert - MQSeries and WebSphere MQ Integrator
Hi Eddie:
I edited the REMOTEQMGR which I meant also QMGR-Full-Repos (sorry for the confusions) . Thanks
-------
PeterPotkay
grand master
Joined: 15 May 2001
Posts: 2734
Location: Hartford CT
Posted: Sat Mar 18, 2006 5:11 pm Post subject:
--------------------------------------------------------------------------------
mikeHT wrote:
I used qload to put the 36 msg to the TRANSMIT.QUEUE and they did not go to the QMGR-Full-repos yet
wha??? Are you opening and putting messages directly into "SYSTEM.CLUSTER.TRANSMIT.QUEUE"?
_________________
Peter Potkay
Amazing MQSeries secrets found here: Click Me
kevinf2349
grand master
Joined: 28 Feb 2003
Posts: 579
Location: USA
Posted: Sat Mar 18, 2006 5:26 pm Post subject:
--------------------------------------------------------------------------------
Quote:
I used qload to put the 36 msg to the TRANSMIT.QUEUE and they did not go to the QMGR-Full-repos yet
Yikes!
-----
Hi Peter & Kevin & others who have issue with get/put msg to SYSTEM.CLUSTER.TRANSMIT.QUEUE:
Yes I did that because I had to backup the messages which I want to keep and which I can't reproduce. I'm not a MQ developer. I used qload (IBM supportpack by Mr Paul Clarke) backup/reload the mssages to transmit.queue.
Everyone:
Just for your information, at 15:32 the 36 msgs which I put back to transmit.queue went through to QMGR-Full-Repos. (Please check the Logs which I pasted below, at 15:23, the clusrcvr queue restarted as if all of a sudden, the messages decided to go off, that was not manually induced)
I'm now suspecting if it is the applications (4 of them) which are causing improper locks (not properly commiting) against the transmit.queue. But again, I did stop the clussdr channel with resolve/commit/reset and at that time, msgs still stuck in transmit.queue.
I did clear all the locks to the transmit.queue, cleared transmit.queue. Restarted the LocalQMGR and checked that the cluster is working OK, used qload to put the 36 msg back to transmit queue. What did the qload do which the applications did not do?
My chl discint is set to 6000 (default), should I be changing it to lower? or should I check/change the DEFBIND properties? Thanks.
dis qs(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
18 : dis qs(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) IPPROCS(2)
OPPROCS(2) CURDEPTH(35)
UNCOM(YES)
dis qs(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
20 : dis qs(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) IPPROCS(1)
OPPROCS(14) CURDEPTH(0)
UNCOM(NO)
dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
21 : dis ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
AMQ8409: Display Queue details.
DESCR(WebSphere MQ Cluster Transmission Queue)
PROCESS( ) BOQNAME( )
INITQ( ) TRIGDATA( )
CLUSTER( ) CLUSNL( )
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) CRDATE(2006-03-16)
CRTIME(08.27.52) ALTDATE(2006-03-1
ALTTIME(13.39.0 GET(ENABLED)
PUT(ENABLED) DEFPRTY(0)
DEFPSIST(NO) MAXDEPTH(999999999)
MAXMSGL(100000000) BOTHRESH(0)
SHARE DEFSOPT(SHARED)
HARDENBO MSGDLVSQ(PRIORITY)
RETINTVL(999999999) USAGE(XMITQ)
TRIGGER TRIGTYPE(FIRST)
TRIGDPTH(1) TRIGMPRI(0)
QDEPTHHI(80) QDEPTHLO(20)
QDPMAXEV(ENABLED) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QSVCINT(999999999)
QSVCIEV(NONE) DISTL(YES)
NPMCLASS(NORMAL) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(1)
OPPROCS(14) CURDEPTH(0)
dis qs(SYSTEM.CLUSTER.TRANSMIT.QUEUE) type(handle) all
22 : dis qs(SYSTEM.CLUSTER.TRANSMIT.QUEUE) type(handle) all
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(18428)
APPLTAG(Appl3) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(20316)
APPLTAG(Appl1) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(22136)
APPLTAG(Appl2) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(12292)
APPLTAG(Appl1) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(12292)
APPLTAG(Appl1) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(15476)
APPLTAG(Appl2) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(20316)
APPLTAG(Appl1) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(20160)
APPLTAG(Appl1) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(20160)
APPLTAG(Appl1) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(14120)
APPLTAG(Appl2) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(19444)
APPLTAG(Appl2) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(4840)
APPLTAG(Appl1) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(4840)
APPLTAG(Appl1) TID(*)
APPLTYPE(USER) CHANNEL()
CONNAME() BROWSE(NO)
INPUT(NO) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(SYSTEM@NT AUTHORITY)
AMQ8450: Display queue status details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) PID(11588)
APPLTAG(ebSphere MQ\bin\amqrrmfa.exe) TID(1)
APPLTYPE(SYSTEM) CHANNEL()
CONNAME() BROWSE(YES)
INPUT(SHARED) INQUIRE(NO)
OUTPUT(YES) SET(NO)
USERID(MUSR_MQADMIN@PLN-CRD-RPTR2)
-------------------------------------------------------------------------------
3/18/2006 15:20:18
AMQ9001: Channel 'TO.LocalQMGR' ended normally.
EXPLANATION:
Channel 'TO.LocalQMGR' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
3/18/2006 15:32:12
AMQ9002: Channel 'TO.LocalQMGR' is starting.
EXPLANATION:
Channel 'TO.LocalQMGR' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
3/18/2006 15:32:12
AMQ9428: Unexpected publication of a cluster queue object received.
EXPLANATION:
The local queue manager has received a publication of a cluster queue object
from a remote queue manager on cluster CLUSTERNAME. The local queue manager discards
the request because it does not host a repository for cluster CLUSTERNAME and has not
subscribed to the published object. The remote CLUSSDR channel used to access
the local queue manager has a channel name of TO.LocalQMGR and the remote queue
manager has a QMID of QMGR-Full-Repos_2005-05-18_15.23.51.
ACTION:
Check the definitions on the local and remote queue managers to ensure that the
CLUSSDR channel points to a repository queue manager for the cluster.
----- amqrrmfa.c : 5590 -------------------------------------------------------
3/18/2006 15:32:12
AMQ9428: Unexpected publication of a cluster queue object received.
EXPLANATION:
The local queue manager has received a publication of a cluster queue object
from a remote queue manager on cluster CLUSTERNAME. The local queue manager discards
the request because it does not host a repository for cluster CLUSTERNAME and has not
subscribed to the published object. The remote CLUSSDR channel used to access
the local queue manager has a channel name of TO.LocalQMGR and the remote queue
manager has a QMID of QMGR-Full-Repos_2005-05-18_15.23.51.
ACTION:
Check the definitions on the local and remote queue managers to ensure that the
CLUSSDR channel points to a repository queue manager for the cluster.
----- amqrrmfa.c : 5590 -------------------------------------------------------
3/18/2006 17:12:13
AMQ9545: Disconnect interval expired.
EXPLANATION:
Channel 'TO.QMGR-Full-Repos' closed because no messages arrived on the transmission
queue within the disconnect interval period.
ACTION:
None.
-------------------------------------------------------------------------------
3/18/2006 17:12:13
AMQ9001: Channel 'TO.QMGR-Full-Repos' ended normally.
EXPLANATION:
Channel 'TO.QMGR-Full-Repos' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
3/18/2006 17:12:13
AMQ9545: Disconnect interval expired.
EXPLANATION:
Channel 'TO.LocalQMGR' closed because no messages arrived on the transmission
queue within the disconnect interval period.
ACTION:
None.
-------------------------------------------------------------------------------
3/18/2006 17:12:13
AMQ9001: Channel 'TO.LocalQMGR' ended normally.
EXPLANATION:
Channel 'TO.LocalQMGR' ended normally.
ACTION:
None.
------------------------------------------------------------------------------- |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Mar 19, 2006 7:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guess I was suggesting that you had clipped the data from amqsbcg too soon. The MQXQH is about 100 bytes and then the full original MQMD. You only posted 32.
It sounds like your applications are not properly committing their messages, though. Stopping the channel with commit is not going to commit messages on the transmit queue unless it's the MCA that has them in a LUW. If your apps aren't committing the PUTs they do (which end up on the SCTQ), then the MCA won't be able to engage those messages in it's own logical units of work.
But on the other hand, you shouldn't have been able to get them with the q program if they weren't committed either.
So then it doens't sound like it's a transaction problem with the application. Which leaves me back to wondering about the destination qmgr name in the MQXQH.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
