ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » Cluster puzzlement: Displaying a cluster in MQExplorer...

Post new topic  Reply to topic
 Cluster puzzlement: Displaying a cluster in MQExplorer... « View previous topic :: View next topic » 
Author Message
aboggis
PostPosted: Tue Sep 16, 2003 1:51 pm    Post subject: Cluster puzzlement: Displaying a cluster in MQExplorer... Reply with quote

Centurion

Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California

I have a cluster with six member queue managers, two full respositories. All on Solaris ( 5.8 ) all running WMQ 5.2, CSD06.

I am viewing the queue manager details using MQExplorer running on my Win2000 workstation (no local queue managers).

When I add a cluster to the "Clusters" node on the MQExplorer, I specify the cluster name & one of the full repositories. It goes "discovering" and comes back with all but one of the queue managers in the cluster. It does however correctly identify both repositories.

I then add the same cluster name again, this time specifying the other repository queue manager. This time ALL six queue managers are "discovered".

I've checked the CLUSSDR/CLUSRCVR pairs on the queue managers and I can't see any obvious...

QM1R (Repository #1 - which shows only 5 members):
CLUSRCVR:TO.QM1R
CLUSSDR:TO.QM2R

QM1 (which shows up in both cases) has:
CLUSRCVR:TO.QM1
CLUSSDR:TO.QM1R

QM1C (which shows up in both cases) has:
CLUSRCVR:TO.QM1C
CLUSSDR:TO.QM1R

QM2R (Repository #2 - which shows all 6 members):
CLUSRCVR:TO.QM2R
CLUSSDR:TO.QM1R

QM2 (which only show up in one) has:
CLUSRCVR:TO.QM2
CLUSSDR:TO.QM2R

QM2C (which shows up in both cases) has:
CLUSRCVR:TO.QM2C
CLUSSDR:TO.QM2R

So, of cource I check the queue manager logs (/var/mqm/qmgrs/<QMGRNAME>/errors and the same error shows in both logs:

Code:
09/16/03  02:01:19 PM
AMQ9418: Only one repository for cluster CLUSTER2B.

EXPLANATION:
The queue manager has received information about a cluster for which it is the
only repository.
ACTION:
Alter the REPOS or REPOSNL attribute of the queue manager, that is to have the
second full repository for the cluster, to specify the cluster name.


So, I hop over to 'runmqsc' on QM1R:

Code:
DIS QMGR ALL
     1 : DIS QMGR ALL
AMQ8408: Display Queue Manager details.
   DESCR( )                                DEADQ(SYSTEM.DEAD.LETTER.QUEUE)
   DEFXMITQ( )                             CHADEXIT( )
   CLWLEXIT(...)
   CLWLDATA( )                             REPOS(CLUSTER2B)


The I do the same on QM2R:

Code:
DIS QMGR ALL
     1 : DIS QMGR ALL
AMQ8408: Display Queue Manager details.
   DESCR( )                                DEADQ(SYSTEM.DEAD.LETTER.QUEUE)
   DEFXMITQ( )                             CHADEXIT( )
   CLWLEXIT(...)
   CLWLDATA( )                             REPOS(CLUSTER2B)


I issue a REFRESH CLUSTER command and both report that they successfully refreshed information...

When I right click and view properties in the MQExplorer, both repositories show that they are members of the same cluster and that they are both full repositories.

Any suggestions?

tonyB.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
PeterPotkay
PostPosted: Tue Sep 16, 2003 4:52 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7717

Issue the DISPLAY CLUSQMGR(qmname) ALL for all 6 queue managers and post the results.

Get yourself up to MQ5.3 if you are going to be doing clusters. It fixed a bunch of known issues for us.

You can never trust the MQExplorer GUI 100% when it comes to clustering. Always double check the slightest doubt with the actual runmqsc commands.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
aboggis
PostPosted: Tue Sep 16, 2003 6:52 pm    Post subject: Reply with quote

Centurion

Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California

Here's all six:

Code:
DISPLAY CLUSQMGR(CLUSTER2B.AR1.MANAGER)
    13 : DISPLAY CLUSQMGR(CLUSTER2B.AR1.MANAGER)
AMQ8441: Display Cluster Queue Manager details.
   CLUSQMGR(CLUSTER2B.AR1.MANAGER)         CLUSTER(CLUSTER2B)
   CHANNEL(TO.AR1)                         CONNAME(192.168.227.42(1414))
   QMID(CLUSTER2B.AR1.MANAGER_2003-08-14_10.01.15)
   DESCR(Cluster-receiver channel for queue manager CLUSTER2B.AR1.MANAGER)
   CLUSTIME(10.01.23)                      CLUSDATE(2003-08-14)
   ALTTIME(17.07.58)                       ALTDATE(2003-09-16)
   TRPTYPE(TCP)                            DEFTYPE(CLUSRCVR)
   QMTYPE(REPOS)                           MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(0)
   SHORTRTY(10)                            SHORTTMR(6)
   LONGRTY(999999999)                      LONGTMR(10)
   SCYEXIT( )                              SCYDATA( )
   SEQWRAP(999999999)                      MAXMSGL(4194304)
   PUTAUT(DEF)                             CONVERT(NO)
   MCAUSER( )                              MCATYPE(THREAD)
   MREXIT( )                               MRDATA( )
   MRRTY(10)                               MRTMR(1000)
   HBINT(60)                               BATCHINT(0)
   NPMSPEED(FAST)                          NETPRTY(0)
   SUSPEND(NO)                         
   SENDEXIT( )                         
   SENDDATA( )                         
   MSGEXIT( )                           
   MSGDATA( )                           
   RCVEXIT( )                           
   RCVDATA( )                           

DISPLAY CLUSQMGR(CLUSTER2B.AS1.MANAGER)
     2 : DISPLAY CLUSQMGR(CLUSTER2B.AS1.MANAGER)
AMQ8441: Display Cluster Queue Manager details.
   CLUSQMGR(CLUSTER2B.AS1.MANAGER)         CLUSTER(CLUSTER2B)
   CHANNEL(TO.AS1)                         CONNAME(192.168.227.45(1414))
   QMID(CLUSTER2B.AS1.MANAGER_2003-08-14_09.59.20)
   DESCR(Cluster-receiver channel for queue manager CLUSTER2B.AS1.MANAGER)
   CLUSTIME(09.59.27)                      CLUSDATE(2003-08-14)
   ALTTIME(09.59.27)                       ALTDATE(2003-08-14)
   TRPTYPE(TCP)                            DEFTYPE(CLUSRCVR)
   QMTYPE(NORMAL)                          MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(0)
   SHORTRTY(10)                            SHORTTMR(6)
   LONGRTY(999999999)                      LONGTMR(10)
   SCYEXIT( )                              SCYDATA( )
   SEQWRAP(999999999)                      MAXMSGL(4194304)
   PUTAUT(DEF)                             CONVERT(NO)
   MCAUSER( )                              MCATYPE(THREAD)
   MREXIT( )                               MRDATA( )
   MRRTY(10)                               MRTMR(1000)
   HBINT(60)                               BATCHINT(0)
   NPMSPEED(FAST)                          NETPRTY(0)
   SUSPEND(NO)                         
   SENDEXIT( )                         
   SENDDATA( )                         
   MSGEXIT( )                           
   MSGDATA( )                           
   RCVEXIT( )                           
   RCVDATA( )                           

DISPLAY CLUSQMGR(CLUSTER2B.AS1C.MANAGER)
     1 : DISPLAY CLUSQMGR(CLUSTER2B.AS1C.MANAGER)
AMQ8441: Display Cluster Queue Manager details.
   CLUSQMGR(CLUSTER2B.AS1C.MANAGER)        CLUSTER(CLUSTER2B)
   CHANNEL(TO.AS1C)                        CONNAME(192.168.227.45(1415))
   QMID(CLUSTER2B.AS1C.MANAGER_2003-08-14_10.00.17)
   DESCR(Cluster receiver channel for queue mgr CLUSTER2B.AS1C.MANAGER)
   CLUSTIME(10.00.24)                      CLUSDATE(2003-08-14)
   ALTTIME(13.15.35)                       ALTDATE(2003-09-16)
   TRPTYPE(TCP)                            DEFTYPE(CLUSRCVR)
   QMTYPE(NORMAL)                          MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(0)
   SHORTRTY(10)                            SHORTTMR(6)
   LONGRTY(999999999)                      LONGTMR(10)
   SCYEXIT( )                              SCYDATA( )
   SEQWRAP(999999999)                      MAXMSGL(4194304)
   PUTAUT(DEF)                             CONVERT(NO)
   MCAUSER( )                              MCATYPE(THREAD)
   MREXIT( )                               MRDATA( )
   MRRTY(10)                               MRTMR(1000)
   HBINT(60)                               BATCHINT(0)
   NPMSPEED(FAST)                          NETPRTY(0)
   SUSPEND(NO)                         
   SENDEXIT( )                         
   SENDDATA( )                         
   MSGEXIT( )                           
   MSGDATA( )                           
   RCVEXIT( )                           
   RCVDATA( )                           

DISPLAY CLUSQMGR(CLUSTER2B.AR2.MANAGER)
     1 : DISPLAY CLUSQMGR(CLUSTER2B.AR2.MANAGER)
AMQ8441: Display Cluster Queue Manager details.
   CLUSQMGR(CLUSTER2B.AR2.MANAGER)         CLUSTER(CLUSTER2B)
   CHANNEL(TO.AR2)                         CONNAME(192.168.227.43(1414))
   QMID(CLUSTER2B.AR2.MANAGER_2003-08-14_10.02.13)
   DESCR(Cluster-receiver channel for queue manager CLUSTER2B.AR2.MANAGER)
   CLUSTIME(10.02.20)                      CLUSDATE(2003-08-14)
   ALTTIME(10.02.20)                       ALTDATE(2003-08-14)
   TRPTYPE(TCP)                            DEFTYPE(CLUSRCVR)
   QMTYPE(REPOS)                           MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(0)
   SHORTRTY(10)                            SHORTTMR(6)
   LONGRTY(999999999)                      LONGTMR(10)
   SCYEXIT( )                              SCYDATA( )
   SEQWRAP(999999999)                      MAXMSGL(4194304)
   PUTAUT(DEF)                             CONVERT(NO)
   MCAUSER( )                              MCATYPE(THREAD)
   MREXIT( )                               MRDATA( )
   MRRTY(10)                               MRTMR(1000)
   HBINT(60)                               BATCHINT(0)
   NPMSPEED(FAST)                          NETPRTY(0)
   SUSPEND(NO)                         
   SENDEXIT( )                         
   SENDDATA( )                         
   MSGEXIT( )                           
   MSGDATA( )                           
   RCVEXIT( )                           
   RCVDATA( )                           

DISPLAY CLUSQMGR(CLUSTER2B.AS2.MANAGER)
     1 : DISPLAY CLUSQMGR(CLUSTER2B.AS2.MANAGER)
AMQ8441: Display Cluster Queue Manager details.
   CLUSQMGR(CLUSTER2B.AS2.MANAGER)         CLUSTER(CLUSTER2B)
   CHANNEL(TO.AS2)                         CONNAME(192.168.227.46(1414))
   QMID(CLUSTER2B.AS2.MANAGER_2003-08-14_10.02.22)
   DESCR(Cluster receiver channel to AS2)
   CLUSTIME(13.28.59)                      CLUSDATE(2003-09-16)
   ALTTIME( )                              ALTDATE( )
   TRPTYPE(TCP)                            DEFTYPE(CLUSRCVR)
   QMTYPE(NORMAL)                          MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(6000)
   SHORTRTY(10)                            SHORTTMR(60)
   LONGRTY(999999999)                      LONGTMR(1200)
   SCYEXIT( )                              SCYDATA( )
   SEQWRAP(999999999)                      MAXMSGL(4194304)
   PUTAUT(DEF)                             CONVERT(NO)
   MCAUSER( )                              MCATYPE(THREAD)
   MREXIT( )                               MRDATA( )
   MRRTY(10)                               MRTMR(1000)
   HBINT(300)                              BATCHINT(0)
   NPMSPEED(FAST)                          NETPRTY(0)
   SUSPEND(NO)                         
   SENDEXIT( )                         
   SENDDATA( )                         
   MSGEXIT( )                           
   MSGDATA( )                           
   RCVEXIT( )                           
   RCVDATA( )                           


DISPLAY CLUSQMGR(CLUSTER2B.AS2C.MANAGER)
     1 : DISPLAY CLUSQMGR(CLUSTER2B.AS2C.MANAGER)
AMQ8441: Display Cluster Queue Manager details.
   CLUSQMGR(CLUSTER2B.AS2C.MANAGER)        CLUSTER(CLUSTER2B)
   CHANNEL(TO.AS2C)                        CONNAME(192.168.227.46(1415))
   QMID(CLUSTER2B.AS2C.MANAGER_2003-08-14_10.03.21)
   DESCR(Cluster-receiver channel for contingency CLUSTER2B.AS2.MANAGER)
   CLUSTIME(10.03.33)                      CLUSDATE(2003-08-14)
   ALTTIME(10.03.33)                       ALTDATE(2003-08-14)
   TRPTYPE(TCP)                            DEFTYPE(CLUSRCVR)
   QMTYPE(NORMAL)                          MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(0)
   SHORTRTY(10)                            SHORTTMR(6)
   LONGRTY(999999999)                      LONGTMR(10)
   SCYEXIT( )                              SCYDATA( )
   SEQWRAP(999999999)                      MAXMSGL(4194304)
   PUTAUT(DEF)                             CONVERT(NO)
   MCAUSER( )                              MCATYPE(THREAD)
   MREXIT( )                               MRDATA( )
   MRRTY(10)                               MRTMR(1000)
   HBINT(60)                               BATCHINT(0)
   NPMSPEED(FAST)                          NETPRTY(0)
   SUSPEND(NO)                         
   SENDEXIT( )                         
   SENDDATA( )                         
   MSGEXIT( )                           
   MSGDATA( )                           
   RCVEXIT( )                           
   RCVDATA( )                           


What seems to be happening right now is that can see the cluster queues (that are local to AS1) from AR1... but when I send messages from a client connected to AR1 they get stuck on the cluster transmit queue even though the send channel is active...
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
PeterPotkay
PostPosted: Wed Sep 17, 2003 4:33 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7717

You issued DISPLAY CLUSQMGR(queuemanagername). I needed you to issue DISPLAY (CLUSQMGR(queuenanager) ALL. Yes its a lot of output, but its kinda hard to debug cluster problems remotely, so all this info helps.




Aha, you said "is that can see the cluster queues (that are local to AS1) from AR1... "

HOW do you see them? Thru MQExplorer right???

MQExplorer cheats! When it gives you the view of the cluster queues for a QM, not only does it show everything that that QM is currently aware of, but it tries to be smart and goes ahead and connects behind the scenes to the full repository and brings over (just for its display to you) what it thinks you should eventually see.

So lets see exactly how AR1 sees those AS1 queues. On AR1, for the problem queue, issue DISPLAY QCLUSTER(yourqname) ALL. And then do the same thing on AS1. Please post and lets compare the 2.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
aboggis
PostPosted: Wed Sep 17, 2003 7:29 am    Post subject: Reply with quote

Centurion

Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California

Hmmm. All I can say at this point is "bugger".

I ran out of time to troubleshoot this issue so I deleted the qmgrs and restored their original configs from backup scripts. I hated having to do that since it's not solving the problem and doesn't really help me identify the root cause.

Quote:
Aha, you said "is that can see the cluster queues (that are local to AS1) from AR1... "


No this was from runmqsc on one of the full repos qmgrs (CLUSTER2B.AR1.MANAGER). I could do a DIS QCLUSTER(AS1*) and it would display the shared (cluster) queues that are hosted on CLUSTER2B.AS1.MANAGER. If I then chose a particular one and did a DIS QCLUSTER(AS1xxx) ALL, it would correctly show CLUSTER2B.AS1.MANAGER as the hosting qmgr. The final oddity at this point was that everything started up and I could show that cluster sender/receiver channels were up and running and using SYSTEM.CLUSTER.TRANSMIT.QUEUE. BUT, when I posted messages from a client attached to CLUSTER2B.AR1.MANAGER, to cluster queues hosted on CLUSTER2B.AS1.MANAGER, they would simply pile up in SYSTEM.CLUSTER.TRANSMIT.QUEUE. I had no further errors in any of the error logs (both the "global" log or the qmgr "local" log).

Still I plan on trying this again when I have a larger window of opportunity and no developers breathing down my neck

I now know that I really shouldn't trust MQExplorer.

Thanks for the reponse Peter.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » Cluster puzzlement: Displaying a cluster in MQExplorer...
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.