| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Yet again,problem with the cluster channels |
« View previous topic :: View next topic » |
| Author |
Message
|
| asalema |
 Posted: Thu Jun 26, 2003 3:39 pm Post subject: Yet again,problem with the cluster channels |
 |
|
Apprentice
Joined: 05 May 2003
Posts: 35
|
Hi All,
We have a problem in production. We have a large cluster that connects 10 QMs with 2 repository QMs.
We noticed if one machine gets rebooted, the repository would loose the connection with that QM, and the channel between the repository QM and this machine has to be restarted manually once the box is up.
I have changed all the explicit channels to have
Short retry count =99999
Short retry interval = 2
so all explicit channels should retry almost forever, once they loose connection.
The problem now is with the automatically generated cluster channels, they use the default values
Short retry count =10
Short retry interval = 60
which disconnects these channels after 10 minutes.
Anyone has any work around for this?.
I did clear the cluster information several times so the automatically generated channels pick up the changed values, but they seem to use the default values regardless.
Regards,
Amr |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Thu Jun 26, 2003 6:22 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
I may be missing something here. But my understanding is of this problem is as below.
When you reboot your machine, which i assume holds the non-repository qm, you start your qm after reboot. And then you manually start the clussdr channel there. Once you do that, the clussdr(autodefined) at the full repository should automatically start itself.
I am not sure thus, what the problem is here.
I dont think there is any other way other than manually starting at least the clussdr channel at the non-repos qm.
Hope this helps.
Cheers
Kumar |
|
| Back to top |
|
|
| bduncan |
| Posted: Fri Jun 27, 2003 11:16 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Also, don't the auto defined cluster channels model their attributes after some SYSTEM.DEFAULT object? If you alter that object, the presumeably all the auto-defined channels will inherit its timeout values, etc...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| asalema |
| Posted: Fri Jun 27, 2003 1:50 pm Post subject: Yet again,problem with the cluster channels |
|
|
Apprentice
Joined: 05 May 2003
Posts: 35
|
Hi Kumar,
Thx very much for your reply. That SYS.DEF.CLSSDR could be it, I will try to alter this definition and see what happens.
Thx again |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jun 30, 2003 6:16 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The clustersenders that are automatically defined between QMs in a cluster get ALL their attributes from the CLUSRCVR they are connecting to. If you want the dynamically created CLUSSNDRs to be created with certain values, make sure you change the CLUSRCVRs.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
