Author |
Message
|
aditya.aggarwal |
Posted: Tue Jun 15, 2010 12:46 pm Post subject: |
|
|
 Master
Joined: 13 Jan 2009 Posts: 252
|
Mod's please move the topic to Clustering Forum.
Thanks.
just changing the scenario lil bit..
We had QMGR.A and a local queue QUEUE.A, this local queue was shared in a cluster. We created the QMGR.B (QMGR.B is same as QMGR.A only name is different and created in different host) added it in to same MQ Cluster.
so now QUEUE.A is locally present at QMGR.B and QMGR.A and a cluster queue.
What will happen in below scenario when a application at QMGR.C (present in same Cluster is trying to put message in Cluster Queue QUEUE.A :
1. QUEUE.A at QMGR.A is put disabled.
2. QUEUE.A is put enabled at QMGR.A and QMGR.B
3. QUEUE.A is put enabled at QMGR.A and QMGR.B But QUEUE.A at QMGR.A is defined as Persistant but QUEUE.A at QMGR.B is defined as non-persistant.
Cheers,
Adi |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jun 15, 2010 12:52 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Split from this _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jun 15, 2010 12:54 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
aditya.aggarwal wrote: |
just changing the scenario lil bit.. |
No, this is a completely different situation. Unless you've deleted one of the queue managers and forgotten to mention it...
aditya.aggarwal wrote: |
What will happen in below scenario when a application at QMGR.C (present in same Cluster is trying to put message in Cluster Queue QUEUE.A :
|
Exactly what the Cluster manual says will happen in each of the scenarios  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
shashivarungupta |
Posted: Wed Jun 16, 2010 2:53 am Post subject: |
|
|
 Grand Master
Joined: 24 Feb 2009 Posts: 1343 Location: Floating in space on a round rock.
|
hah....
I think.. aditya is trying to state that if a clustered queue (with multiple instances i.e. exists on two/more queue managers in that cluster ) which is put disabled on one of the clustered queue managers then message would round robin to other cluster queue manager..
and in case QMGR.A does not exist in the cluster anymore then messages won't go to QUEUE.A of QMGR.A and messages would/should go to QUEUE.A of QMGR.B
I believe he is trying to corelate the Logic.
Thanks.  _________________ *Life will beat you down, you need to decide to fight back or leave it. |
|
Back to top |
|
 |
aditya.aggarwal |
Posted: Wed Jun 16, 2010 5:18 am Post subject: |
|
|
 Master
Joined: 13 Jan 2009 Posts: 252
|
Vitor Wrote:
Quote: |
Unless you've deleted one of the queue managers and forgotten to mention it |
Queue managers is not deleted.
Vitor Wrote:
Quote: |
aditya.aggarwal wrote:
What will happen in below scenario when a application at QMGR.C (present in same Cluster is trying to put message in Cluster Queue QUEUE.A :
Exactly what the Cluster manual says will happen in each of the scenarios |
I think point 3 is not discussed in manuals..
What will happen in below situation when a application at QMGR.C (present in same Cluster is trying to put message in Cluster Queue QUEUE.A
3. QUEUE.A is put enabled at QMGR.A and QMGR.B But QUEUE.A at QMGR.A is defined as Persistant but QUEUE.A at QMGR.B is defined as non-persistant. |
|
Back to top |
|
 |
exerk |
Posted: Wed Jun 16, 2010 5:30 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
The inconsistency will be reported in the queue manager logs, but the inconsistency will not affect the load-balancing of the cluster (assuming BIND(NOTFIXED)). _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jun 16, 2010 5:32 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
aditya.aggarwal wrote: |
I think point 3 is not discussed in manuals..
|
Really? You should raise a PMR against the documentation... _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Jun 16, 2010 6:08 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
I think point 3 is not discussed in manuals..
What will happen in below situation when a application at QMGR.C (present in same Cluster is trying to put message in Cluster Queue QUEUE.A
3. QUEUE.A is put enabled at QMGR.A and QMGR.B But QUEUE.A at QMGR.A is defined as Persistant but QUEUE.A at QMGR.B is defined as non-persistant. |
This, and the other hypotheticals you have posted , are documented in the manuals, and are things you can test.
While we are willing and able to help you with problems, we encourage you to do your own reading and research first before posting.
I strongly suggest that you read, experiment, test, re-read, test some more; then post your results. _________________ 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 |
|
 |
fatherjack |
Posted: Wed Jun 16, 2010 8:46 am Post subject: |
|
|
 Knight
Joined: 14 Apr 2010 Posts: 522 Location: Craggy Island
|
aditya.aggarwal wrote: |
3. QUEUE.A is put enabled at QMGR.A and QMGR.B But QUEUE.A at QMGR.A is defined as Persistant but QUEUE.A at QMGR.B is defined as non-persistant. |
Queues are not persistent or non-persistent. Messages are. _________________ Never let the facts get in the way of a good theory. |
|
Back to top |
|
 |
shashivarungupta |
Posted: Thu Jun 17, 2010 4:05 am Post subject: |
|
|
 Grand Master
Joined: 24 Feb 2009 Posts: 1343 Location: Floating in space on a round rock.
|
fatherjack wrote: |
aditya.aggarwal wrote: |
3. QUEUE.A is put enabled at QMGR.A and QMGR.B But QUEUE.A at QMGR.A is defined as Persistant but QUEUE.A at QMGR.B is defined as non-persistant. |
Queues are not persistent or non-persistent. Messages are. |
"When you create a message, if you initialize the message descriptor (MQMD) using the defaults, the persistence for the message is taken from the DefPersistence attribute of the queue specified in the MQOPEN command. Alternatively, you can set the persistence of the message using the Persistence field of the MQMD structure to define the message as persistent or nonpersistent."  _________________ *Life will beat you down, you need to decide to fight back or leave it. |
|
Back to top |
|
 |
|