| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| What is failover, maybe that's not what i want. |
« View previous topic :: View next topic » |
| Author |
Message
|
| GregJ |
 Posted: Mon Mar 22, 2004 7:28 am Post subject: What is failover, maybe that's not what i want. |
 |
|
Acolyte
Joined: 24 Oct 2001
Posts: 69
Location: Markham, On. Canada
|
Maybe i'm not clear what the true definition of failover is... but in reading the "MQSeries Primer" Page 11 states this:
In another scenario involving queue B, we notice that the third queue manager is down and the third instance of queue B is not available. The sending queue manager becomes aware of this problem because it subscribed to information about all queue manager and queues it is interested in, that is, where it sends messages. As soon as it finds out that there is a problem with the third instance of B, it distributes messages to the first two instances only. Special messages about changes of the status of cluster objects are instantly published to all queue managers that
subscribed to that object.
That's what i need, if one queue manager is not responding, I want everything diverted to another. It may not be 'failover' per se, but will clustering achieve this? or would "distribution lists'" be an easier route.
Thanks[/quote] |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Mon Mar 22, 2004 7:44 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
if you are fine with so called 'stuck' messages (messages not being
processed on a certain queuemanager but already on that queuemanager
having a 'problem') during failover then clustering will do fine.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| EddieA |
| Posted: Mon Mar 22, 2004 9:15 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| or would "distribution lists'" be an easier route |
This option would send the SAME message to multiple Queue Managers.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| offshore |
| Posted: Tue Mar 23, 2004 9:39 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
I haven't dove into the world of distribution lists yet, but I will tell you what I know about clustering and message redirection.
| Quote: |
| As soon as it finds out that there is a problem with the third instance of B, it distributes messages to the first two instances only. |
For this to work the cluster queues will have to be defined with DEFBIND(NOTFIXED). This will allow MQ to manipulate the messages <in SYSTEM.CLUSTER.TRANSMIT.QUEUE> that were destined for the 3rd instance of "B"/QMGR3 and redirect it to another available QMGR that also hosts "B"
*Note when you defined a QL the default valued o DEFBIND is OPEN.*
Or if the application does a put it does a MQPUT1 this will always act if DEBIND(NOTFIXED) is specified.
Another good source of info is
1) WebSphere MQ Queue Manager Clusters manual
2) WebSphere MQ for z/OS in Parallel Sysplex Environment.
CH. 7 specifically deals w/ clustering.
HTH |
|
| 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
|
|
|
|
