| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Consequences of creating 2 CLUSSDR channels in Queue Manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mangesh1187 |
 Posted: Sun Apr 01, 2018 9:17 pm Post subject: Consequences of creating 2 CLUSSDR channels in Queue Manager |
 |
|
Centurion
Joined: 23 Mar 2013
Posts: 116
|
Hi All,
Created more than one CLUSSDR channel is not recommended. However curious about if accidentally someone created it, what will be consequences of it:
I can imagine 3 scenarios :
#1) If we define only ONE CLUSSDR channel from a partial QM to another partial QM (instead of Full Repos QM)
#2) If we define TWO CLUSSDR channel : one points to Full Repos & other points to partial repos QM.
#3) If we create TWO CLJSSDR channel : both points to separate Full repos queue managers.
As I guess for scenario #1, in this scenario the QM where we create this CLUSSDR channel won't able to know about rest of the QMs & cluster objects.
And hence won't able to participate in cluster.
Curious about the consequences of scenario #2 & #3.
Any thoughts? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Apr 02, 2018 4:22 am Post subject: Re: Consequences of creating 2 CLUSSDR channels in Queue Man |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Mangesh1187 wrote: |
Hi All,
Created more than one CLUSSDR channel is not recommended. However curious about if accidentally someone created it, what will be consequences of it:
I can imagine 3 scenarios :
#1) If we define only ONE CLUSSDR channel from a partial QM to another partial QM (instead of Full Repos QM)
#2) If we define TWO CLUSSDR channel : one points to Full Repos & other points to partial repos QM.
#3) If we create TWO CLJSSDR channel : both points to separate Full repos queue managers.
As I guess for scenario #1, in this scenario the QM where we create this CLUSSDR channel won't able to know about rest of the QMs & cluster objects.
And hence won't able to participate in cluster.
Curious about the consequences of scenario #2 & #3.
Any thoughts? |
Well in your scenario #2, at best the one pointing to the PR gets ignored. At worst it thinks the PR is an FR and nothing really works...
#3 should not be a problem. The second manually defined CLUSSDR will be ignored or vice versa.
Have fun 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
