Author |
Message
|
purohit |
Posted: Fri Apr 04, 2008 4:51 am Post subject: KeepAlive parameter in Windows registry for WMQ6.0 |
|
|
Novice
Joined: 09 Aug 2007 Posts: 18
|
Can i enable KeepAlive parameter in Windows registry?
I have done it Solaris and AIX by adding the TCP stanza in the corresponding qm.ini files of the QMs. But in windows it should be done in the registry. Will there be a key in
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\QueueManager/<QM_Name>
or should it be done in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
I came across KeepAliveTime but u can specify only the time interval there.....i want to know how to enable it, the way we do it in Solaris and AIX, if at all its possible......KeepAlive = Yes |
|
Back to top |
|
 |
Gaya3 |
Posted: Fri Apr 04, 2008 4:54 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
most of the times, its not required at Windows side to set it up
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
purohit |
Posted: Fri Apr 04, 2008 4:57 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007 Posts: 18
|
Ok....but if at all i need to do it then where i should be doing it?? |
|
Back to top |
|
 |
Gaya3 |
Posted: Fri Apr 04, 2008 5:05 am Post subject: Re: KeepAlive parameter in Windows registry for WMQ6.0 |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
purohit wrote: |
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\QueueManager/<QM_Name>
if you are doing it here, it will be the part of queue manager
or should it be done in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
here it will treated as OS service (This sounds good) as TCPKeepAlive is OS Dependent always
|
_________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
purohit |
Posted: Fri Apr 04, 2008 5:52 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007 Posts: 18
|
i can see some folders like Log, Service, TuninigParameters etc under
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\QueueManager\<QM_Name>
should i create some folder for adding the key KeepAlive n then assign it a boolean value? i dont know....i haven't done anything like that before. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Apr 04, 2008 10:43 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Keep Alive is just as valid on Windows Queue Managers as any other Queue Manager providing a similiar function.
Why re you hacking the registry? Use the correct method. Open MQExplorer and set it there! _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
purohit |
Posted: Mon Apr 07, 2008 4:38 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007 Posts: 18
|
but i have to set that parameter using a script and not using MQExplorer. is ther any way to do it??? |
|
Back to top |
|
 |
Vitor |
Posted: Mon Apr 07, 2008 4:47 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
purohit wrote: |
but i have to set that parameter using a script and not using MQExplorer. is ther any way to do it??? |
You can script changes to the registry, but it relies on the set-up being the same on all the target machines. Windows being Windows that's a heck of a reliance.
I don't think we've ever addressed what actual problem you're trying to address here. Why are you trying to set this value? What will it prevent / help with?
There might be a better way. There often is. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
purohit |
Posted: Mon Apr 07, 2008 5:12 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007 Posts: 18
|
all i have is a script (batch file) which creates a QM and start it, defines a listener and start it, defines various channels, enables some events on the QM, creates a key data base and adds a root certificate.
Now i want that TCP KeepAlive parameter to be set through this batch file.
On the other platforms (AIX and Solaris) i am adding the TCP stanza in qm.ini through a script, which does all the things mentioned above like creating QM, enabling events etc. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Apr 07, 2008 5:14 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
purohit wrote: |
Now i want that TCP KeepAlive parameter to be set through this batch file.
|
Yes, I'd got that, but why set TCP KeepAlive on Windows? Through a batch file or otherwise?
Indeed, why set it by default on Unix platforms? What's the requirement? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
purohit |
Posted: Mon Apr 07, 2008 5:21 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007 Posts: 18
|
even i too am not sure why its required but i have been asked to do so .........is there any problem in setting it that way?? |
|
Back to top |
|
 |
Vitor |
Posted: Mon Apr 07, 2008 5:23 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
purohit wrote: |
even i too am not sure why its required but i have been asked to do so .........is there any problem in setting it that way?? |
Well it's pointless at best unless there's a specific issue where you need it. At worst it can cause other problems.
There's also the larger issue of setting parameters for no documented reason. If you don't know why you need it, how will you know if you ever need to change it? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Apr 07, 2008 5:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
KeepAlive is recommended for a number of reasons, including allowing a channel to recover from a bad network outage.
I recently had to assist with such a case, where a network outage had caused the clusrcvr side of a channel to stay at "running" while the corresponding clussdr was in retry".
The end result was to restart the qm on the rcvr side - which happened to be the production broker qmgr, so this was not a small impact! The restart was deemed necessary because attempts to stop the clusrcvr were unsuccessful to the point of needing to STOP CHANNEL mode(FORCE), which would have killed off half the connections into the queue manager... so it was deemed better to kill off all of them gracefully rather than half ungracefully.
KeepAlive would have allowed the clusrcvr to recover. _________________ I am *not* the model of the modern major general.
Last edited by jefflowrey on Mon Apr 07, 2008 5:34 am; edited 1 time in total |
|
Back to top |
|
 |
purohit |
Posted: Mon Apr 07, 2008 5:34 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007 Posts: 18
|
the requirement is to make sure the channel is closed if there is a problem at either of the ends for which you have to enable that parameter!!! |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Apr 07, 2008 6:34 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
We turn Keep Alive on for every one of our QMs. It helps clean up orphaned channel connections (primarily SVRCONNs). I have yet to see a drawback to setting it.
Without it you are more likely to hit Max Active Channels on a QM.
Jeff, your scenario I think could have been avoided if the QMs were using Adopt MCA for their channels. If if there was a hung receiver a new instance of the sender would have been adopted. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|