| Author |
Message
|
| EKhalil |
 Posted: Tue Mar 22, 2005 10:20 am Post subject: SUSPEND QMGR is not working as supposed to |
 |
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
In a testing env. config. there are 2 win/app Qmgrs, 2 win/hub Qmgrs and a 1 z/os Qmgr. z/os Qmgr and of 1 win/hub Qmgr are repos. When SUSPEND QMGR CLUSTER(XYZ) is issued against win/hub Repo Qmgr, it is accepted and log shows successful completion. However, whenever messages are send from 2 win/app Qmgrs they are evenly distributed among 2 win/hub Qmgrs. I thought that by issuing the command against one of the win/hub Qmgrs I will prevent him/her  from accepting any new comming messages...IS THERE SOMETHING that I'm missing here ???
Thanx in advance,
Eva |
|
| Back to top |
|
 |
| sebastianhirt |
| Posted: Tue Mar 22, 2005 2:06 pm Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
Hi Eva,
IBMs Clustering training Materials say, that the suspend will not have any effect, if this is the only chance for your cluster to deliver a message...
Means, if you are putting a message to clusterqueueA and there is only one instance of that queue in the cluster, MQ will deliver the message to clusterqueueA even though the QM is suspended.
Messages might also still be sent to the suspended Queue manager, if the work load algorythm is not finding a suitable alternative.
I hope I explained that right now...
You might also want to check up the Clustering Manual to get more information about how suspension of a queue manager works.
If it is only 1 queue we are talking about, you might want to consider, taking that queue temporaily out of the cluster.
I think the queuemanager is a he. As it is in german "der queue manager", and "der" is male.
Hope this helps
Sebastian |
|
| Back to top |
|
|
| EKhalil |
| Posted: Wed Mar 23, 2005 7:45 am Post subject: Hmmm.... |
|
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
Thanks for your reply. Greatly appreciated.
Well, when I was setting them up I have ran the same script on both win/hub Qmgrs - they have identical objects. (Unfortunately I'm not dealing with only one or several queues.) Went over the command once again as you have suggested, this is what I came accross:"Messages that have to be handled by that queue manager include messages sent by the local queue manager. The workload management routines choose the local queue manager whenever possible, even if it is suspended." What I'm wondering about now is the fact that win/app Qmgrs and repo win/hub guy are actually sitting on one physical machine which is divided into several virtual servers through VMWare...Any thoughts on that ??? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 23, 2005 7:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you want to prevent a queue manager from receiving cluster messages, then remove it from the cluster.
Or stop the listener and the channel initiator.
VMWare is supposed to be transparent to the OS and the apps running in the OS. So there should be no way for those two queue managers to know that they are colocated.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| EKhalil |
| Posted: Wed Mar 23, 2005 8:36 am Post subject: ... |
|
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
Thanks 
I do realize there are different ways of making sure the messages will not be directed to win/hub repo Qmgr. However, I have used the suspend command successfully in many other envirnments and the only difference I was able to pin point so far is the use of virtual servers. My question pertains to why it's not working as supposed to not how to prevent qmgr from taking up work.
As to VMWare you're absolutely right, they should have no idea about existing on the same box...
Anyone have experienced issues with this command ??? |
|
| Back to top |
|
|
| EKhalil |
| Posted: Wed Mar 23, 2005 9:05 am Post subject: more details |
|
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
Anyway just to let you guys know...
This command was ran on win/app Qmgrs : DISPLAY CLUSQMGR(*) CLUSTER(XYZ) SUSPEND and the win/app Qmgrs can not see the virtual win/hub qmgr as a qmgr that has been suspended from the cluster. However if you suspend the other win/hub qmgr (not virtual) and issue the above command, the win/app qmgrs are able to recognize that...and will not forward work to him... |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Mar 23, 2005 10:12 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Eva, what you are doing sounds correct, and it sounds like you have a legitimate gripe.
QMA, QM1 and QM2 are all in the cluster.
If QMA sends messages to QueueEva on QM1 and QM2, and QMA does not host QueueEva itself, QMA will round robin to QM1 and QM2. If you SUSPEND QM1 from the cluster, them QMA should only send to QueueEva on QM2.
If QMA still sends to both QueueEvas, this is a problem. Either you did not issue SUSPEND correctly for QM1, or you have a bug.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| EKhalil |
| Posted: Wed Mar 23, 2005 10:40 am Post subject: A bug ??? |
|
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
Thanks Pete
I'm gonna assume that suspend was issued correctly, cause the log shows successful command completion and the number of suspended objects. I'll keep on digging...and if I'll find what's messing things up I'll let you all know |
|
| Back to top |
|
|
| JMB |
| Posted: Fri Mar 25, 2005 6:31 am Post subject: |
|
|
Apprentice
Joined: 01 Apr 2002
Posts: 29
|
| refreshing the cluster seems to have fixed our problem. |
|
| Back to top |
|
|
|
|
