| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Editing properties of Cluster Channels |
« View previous topic :: View next topic » |
| Author |
Message
|
| Rangarajan |
 Posted: Mon Jul 21, 2003 1:32 am Post subject: Editing properties of Cluster Channels |
 |
|
Novice
Joined: 01 Aug 2002
Posts: 22
|
I created three Qmgrs that form a part of the cluster. Now the IP Address of all the three system is changed. What should i do to make the channels between qmgrs listen to each other?
I tried changing the Connection name in channels and restarted the channels, which i used to do in distributed queing. But still this doesnt work.
Can anyone help me on this?
regards
Rangarajan |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Mon Jul 21, 2003 5:54 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
I have never come accross such a situation myself, but remember that any changes in a clustered environment would NEVER take effect unless you publish the new information again. And this is possible by issuing a "REFRESH CLUSTER". I am not saying that your problem would be solved if you issue this, but theoretically this should. Give it a try which i a positive about.
Cheers
Kumar |
|
| Back to top |
|
|
| bduncan |
| Posted: Mon Jul 21, 2003 8:51 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
It sounds like you defined these channels with the IP addresses in the CONNAME? The MQSeries documentation recommends that you use DNS names rather than IP addresses in the CONNAME so that you avoid exactly the problem that you have right now.
I've run into this problem in the past, and I had to resort to removing each queue manager from the cluster and deleting/recreating their channels to get it to work. If you end up doing this, I recommend using the DNS names when you redefine the channels.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| abanks |
| Posted: Fri Aug 15, 2003 5:29 am Post subject: |
|
|
Newbie
Joined: 04 Apr 2002
Posts: 3
|
This is analagous to two freiends both moving house at roughly the same time and posting their new address to each other's old address. Neither receives the other's new address.
For releases prior to V5.3, the way out of this is to define new CLUSSDR and CLUSRCVR channels with new channel names the new addresses. These allow the changes for the old adresses to flow after which the new channels can be deleted.
For release V5.3 you can alter the existing CLUSRCVR and CLUSSDR definitions to have the new addresses, temporarily change the full repositories to be partial repositories, then execute REFRESH CLUSTER REPOS(YES). The REPOS(YES) part causes the last known address in the full repositories CLUSRCVR to be discarded and the value from the CLUSSDR to be used instead. See Problem 4, in the "Resolving Problems" section of the Queue Manager Clusters manual. |
|
| 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
|
|
|
|
