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 » Duplicate cluster members....

Post new topic  Reply to topic
 Duplicate cluster members.... « View previous topic :: View next topic » 
Author Message
aboggis
PostPosted: Tue Feb 03, 2004 11:11 pm    Post subject: Duplicate cluster members.... Reply with quote

Centurion

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

Environment: Solaris 5.8, WMQ 5.3, CSD05.

This is a development/test environment so sometimes things don't get done "by the book". That said, "the book" doesn't seem to be helping be out of my current situation...

I have the same queue manager in the cluster twice, with the same QMID:

Code:

dis clusqmgr(*) conname qmid
    14 : dis clusqmgr(*) conname qmid
...
AMQ8441: Display Cluster Queue Manager details.
   CLUSQMGR(BMON_QMGR)                CLUSTER(CLUSTER3B)
   CHANNEL(TO.BMON_QMGR)              CONNAME(192.168.226.88(1416))
   QMID(BMON_QMGR_2004-01-15_08.24.56)
AMQ8441: Display Cluster Queue Manager details.
   CLUSQMGR(BMON_QMGR)                CLUSTER(CLUSTER2B)
   CHANNEL(TO.BMON1)                       CONNAME(192.168.226.88(1416))
   QMID(BMON_QMGR_2004-01-15_08.24.56)


As you can see, everything but the channel name is identical for the duplicated entry. This output is from one of the full repositories 'CLUSTER3B.AS1.MANAGER'. The other full repos is on 'CLUSTER3B.AR1.MANAGER'. The duplicated queue manager is just a regular cluster queue manager. It WAS a member of the cluster CLUSTER2B, but was moved into a new cluster (CLUSTER3B), and the offending entry shows this.

Normally I would use the RESET CLUSTER... FORCEREMOVE QMID command in 'runmqsc', but I don't want them both removed.

Displaying all channels on 'CLUSTER3B.AS1.MANAGER' gives the follwing:

Code:

    17 : dis chstatus(TO*)
AMQ8417: Display Channel Status details.
   CHANNEL(TO.BMON1)                       XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
   CONNAME(192.168.226.88(1414))           CURRENT
   CHLTYPE(CLUSSDR)                        STATUS(STOPPED)
   RQMNAME()                           
...


All the other queue managers show only a single instance of this queue manager.

I can't delete the stopped channel since it's an auto-defined cluster channel and doesn't "really exist". Forcing a refresh doesn't seem to do the trick.

Suggestions?
Back to top
View user's profile Send private message AIM Address Yahoo Messenger
TonyD
PostPosted: Wed Feb 04, 2004 2:18 pm    Post subject: Reply with quote

Knight

Joined: 15 May 2001
Posts: 540
Location: New Zealand

You say:
Quote:
...everything but the channel name is identical for the duplicated entry
, but the cluster name is also different for the two entries, and you note that the qmgr used to be a member of CLUSTER2B? Looking at an 'dis clusqmgr' output in my environment shows similar entries when a qmgr belongs to more than one cluster. Have you run 'amqrfdm' in order to see more information?
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » Duplicate cluster members....
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.