| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Add QMgr To Cluster - Seeing Existing Clustered Queues |
« View previous topic :: View next topic » |
| Author |
Message
|
| brpope |
 Posted: Tue Sep 24, 2002 1:42 pm Post subject: Add QMgr To Cluster - Seeing Existing Clustered Queues |
 |
|
Novice
Joined: 01 Aug 2001
Posts: 10
|
I went ahead and tried to add a non-repository qmgr to an existing cluster by defining the cluster sender and cluster receiver channels. The cluster sender channel runs fine (pointing to one of the repository qmgrs). Looking at the properties for the newly added qmgr it appears to belong the the cluster. However, the cluster receiver channel remains inactive and the new qmgr can't see any of the shared queues that already exist within the cluster. Conversely, any local queues I define as shared cluster queues on this new qmgr are not available on any of the existing cluster queue managers.
Any suggestions on what might be preventing this newly added qmgr from seeing the queues already defined within the cluster?
Thanks, Ben |
|
| Back to top |
|
 |
| bduncan |
| Posted: Tue Sep 24, 2002 2:02 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Ben,
There are all sorts of reasons why this may be happening. 99% of the time it turns out something was misconfigured in the queue manager - the rest being some network guy tripping over an ethernet cable, etc.. 
I would consult the queue manager logs. Typically it will list why the listener isn't starting correctly. Next thing, check to see if the amqsbcg process is running. If you are on unix, make sure the inetd and services files are correct (so amqsbcg starts automatically). Also, check the logs for the repository you were trying to connect to. Since the sender on the non-repository started, that means it sent a message to the repository saying "here I am, add me to the cluster". The respository will then try to send messages containing the names of all the objects (queues) in the cluster. This means the repository needs to start a sender channel back to the non-repository machine. See the status of this channel. It's probably inactive or retrying. Check the logs to see why.
Hope this gets you started...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| nimconsult |
| Posted: Wed Sep 25, 2002 4:49 am Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
Do you mean that attempts to open a queue of the cluster fail when you connect to the non-repository queue manager? If yes read the diagnostic of Brandon.
Otherwise if you are just looking at the queue definitions, it is normal that you cannot see the clustered queue definitions. If the new queue manager is not a full repository, the queue definitions will only be loaded when needed.
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
| brpope |
| Posted: Wed Sep 25, 2002 12:39 pm Post subject: |
|
|
Novice
Joined: 01 Aug 2001
Posts: 10
|
Well, I can't see the cluster-queue definitions even if I try to access one. Slogging through the logs I can see messages relating to not being able to start the clusrcvr channel back to my non-repository queue manager. Anyway, I finally tried creating the qmgr on a seperate physical host and following the setup I've been doing all along, it works.
So, back to my original situation (maybe I should have done a better job describing that in the first place <grin>), apparently I'm missing something about running 2-qmgrs on the same physical box (I thought all that was required was setting up the listeners on different ports #'s). Apparently, when clustering enters the picture, something else has to be unique? Basically, I've got two physical hosts. Each has a qmgr running as a repository qmgr. On one of the hosts, I add another qmgr (non-repository). All appears fine, it shows up as belonging to the cluster, its clussdr channel starts fine but it can't see cluster'd queues and its clusrcvr channel remains inactive. I also get contact admin log messages about not being able to access the clusrcvr channel.
Any suggestions on what has to be tweaked with the 2nd qmgr install to make it well-behaved in a cluster?
Thanks, Ben |
|
| Back to top |
|
|
| TonyD |
| Posted: Wed Sep 25, 2002 2:41 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| As far as I know there are no issues with having multiple clustered QMs on the sam machine. Currently I have two repository QMs that belong to a cluster and a third, connected to one of them, that is not in the cluster all running on my PC. The messages about not being able to start the cluster channel should be followed through if possible. In particular beware if you change the listener port for a QM AFTER the cluster channels have been created. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
