| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problems seeing queues in cluster |
« View previous topic :: View next topic » |
| Author |
Message
|
| neeff |
 Posted: Wed Jul 23, 2003 12:36 pm Post subject: Problems seeing queues in cluster |
 |
|
Novice
Joined: 06 Apr 2003
Posts: 11
Location: Munich and Ludwigsburg, Germany
|
Hallo *,
we have a scenario of 4 queue managers in a cluster, two hold a full repository. When creating a new cluster queue on one of the repository queue managers, it appears immedeatly in the Websphere MQ explorer. When trying to display the cluster queues using runmqsc, we have the following scenario:
* on all repository QMs the queue is visible.
* on all other (non-repository QMs) the queue is NOT visible. The display qcluster(queuename) says Websphere MQ object not found.
If I try to do a sample spoolin on a non-repository QM using amqsput, I can access the queue and spool in some stuff. If I run runmqsc after the spoolin on the non repository QM on which I did the spoolin, the queue is visible. On the other non-repos QM the queue is still NOT visible.
We do not understand what is going on here. All cluster sender and receiver queues are running, all SYSTEM.CLUSTER.TRAMSIT.QUEUES have queuedepth 0. We tried to refresh the cluster with repos(YES), still the same. Does anybode have an idea?
Thanks, Thomas
_________________
Thomas Neeff
Certified IBM System Administrator - WebSphere MQ, V5.3
Germany |
|
| Back to top |
|
 |
| oz1ccg |
| Posted: Wed Jul 23, 2003 12:56 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi Thomas,
That's the way it work.
Well, the full repository qmgrs, knows all cluster queues.
The rest of the queuemanagers, only knows their own at the beginning, and after applications opens queues, the queuemanager looks into it's own repository, and if found there it use the information found there.
Then there are the most interesting part, the queue is not know in the local repository; we have to ask the full repos, and if positive, update our own repository.
Why it works this way ? Performance, Performance....... So WMQ Just keep updated information where they are needed. Don't get the idea of making all qmgrs full repositories... Typicly use two, without studying the manual.
I hope this helps you
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Wed Jul 23, 2003 12:59 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
When you define a clustered queue on the full repository queue manager, the queue is published to the non-repositories only on demand. As you already found out. When you issue an amqsput from the non-repos qm, that qm in turn requests for the latest cache info from the full repository. Which then gets updated to this non-repos qm and hence after this you see the clustered queue. And for the same reason you dont see it on the other non-repository qm.
This is not the case when the clustered queues are hosted on non-repository queue mangers. They are published immediately.
So, to conclude, what you see is just normal. It would have been an issue if you did not see the queue, even after you ran amqsput on one of the non-repos qms.
Cheers
Kumar |
|
| Back to top |
|
|
| neeff |
| Posted: Wed Jul 23, 2003 1:07 pm Post subject: |
|
|
Novice
Joined: 06 Apr 2003
Posts: 11
Location: Munich and Ludwigsburg, Germany
|
Hi Jorgen,
thanks for your fast and helpful reply.
The only thing we do not understand is: Why does the Websphere MQ Explorer show all these queues while they are not visible in runmqsc? What is the explorer doing different from runmqsc? Is the explorer getting the information using PCF commands?
I do not like these graphical stuff, but sometimes it is helpful....
Best regards, Thomas
_________________
Thomas Neeff
Certified IBM System Administrator - WebSphere MQ, V5.3
Germany |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Jul 23, 2003 2:12 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
You can see them all in runmqsc. You just need 2 commands:
dis q(*)
dis qc(*)
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| neeff |
| Posted: Thu Jul 24, 2003 8:34 am Post subject: |
|
|
Novice
Joined: 06 Apr 2003
Posts: 11
Location: Munich and Ludwigsburg, Germany
|
Yes - on the repository QM, not on the others.... You may try it on the non-repository QM: as long as you haven't done a spool in to a cluster queue, you won't see it on the non-repos QM. A "dis qcluster(*) will show "Websphere object '*' not found" as long as you didn't do a spool in to a cluster queue hosted by another QM on the non-repos QM.
IBM stated also that this behaviour is normal. Thanks to all who gave input to this question!
Thomas
_________________
Thomas Neeff
Certified IBM System Administrator - WebSphere MQ, V5.3
Germany |
|
| 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
|
|
|
|
