| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SUSPEND all qmgrs == No suspending at all? |
« View previous topic :: View next topic » |
| Author |
Message
|
| issac |
 Posted: Thu May 23, 2013 5:44 pm Post subject: SUSPEND all qmgrs == No suspending at all? |
 |
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Hello,
The phenomenon described bellow has been recreatable in every QMGR v7 on every platform so far. Would you please tell me if you consider it normal or a problem
There are MQA, MQB, MQC in the cluster. A cluster queue APPQ has instances in MQB and MQC. Messages are put to APPQ through MQA.
I suspend MQB, then messages go to MQC. That's right.
I suspend MQC, then messages go to MQB. That's right.
But when I suspend both MQB & MQC, messages would start distributing equally in MQB & MQC.
It feels somewhat weired to me. I opened a PMR to IBM, but locale supports just said it's working by design, which I don't really believe. So I read the InfoCenter, there's no explicit description about this behavior. Does it appear normal to you?
_________________
Bazinga! |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu May 23, 2013 6:19 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9397
Location: US: west coast, almost. Otherwise, enroute.
|
SUSPEND from a qmgr tells other qmgrs "please don't use me as a destination for MQPUTs." Note the "please." If no other instances of the queue are available on other qmgrs, the SUSPENDed qmgrs queues will continue to be chosen as destinations.
What, exactly, feels weird to you? What behavior do you expect?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| issac |
| Posted: Thu May 23, 2013 10:39 pm Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Mmmm... yes. I think you are right. InforCenter says it would "advise" other qmgrs not to send messages.
I thought it would just stop dispatching messages... Now I think the idea is wrong.
_________________
Bazinga! |
|
| Back to top |
|
|
| hughson |
| Posted: Fri May 24, 2013 4:26 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
This is indeed normal.
Suspending a queue manager from a cluster indicates to the cluster workload balancing algorithm that it is a less good choice relative to the other queue managers it can choose from. If all queue managers are suspended then they all become an equally good/bad choice again.
If you want messages to stop being routed to the queue manager you have other choices. Which you take depends on whether you want messages to sit and wait on the transmission queue until queue managers come back available again, or whether you want the application to be given a return code to say that there are no queue managers available to put this message on at all. In this latter case PUT(DISABLE)-ing the cluster queues on each queue manager will do that.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| 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
|
|
|
|
