| Author |
Message
|
| Rahul999 |
 Posted: Sun Jul 18, 2010 12:54 am Post subject: Always mandatory to restart the MB after properties change? |
 |
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Hi All,
Is it always necessary to re-start the message broker after running mqsichangeproperties command(IBM documentation says so), even if you are changing the properties only at Execution Group level and not on BROKER level.
We sometimes have to run mqsichangeproperties to enable Debug port on an execution group or to set tcpipNoDelay on an execution group.
Below are the 2 commands which we use frequently on different environments and different execution groups.
1. mqsichangeproperties BRKBRK1 -e eg1 -o ComIbmSocketConnectionManager -n tcpNoDelay -v true
2. mqsichangeproperties BRKBRK1 -e eg1 -o ComIbmJVMManager -n jvmDebugPort -v 3322
Now the above 2 commands does changes only at execution group level, still I need to re-start the BROKER, or can't we just use "mqsireload" command, which is useful to stop and start execution group processes.
It is very difficult for us to get approval to re-start the complete BROKER, considering the fact that multiple execution groups are running on that BROKER, whereas we are changing properties only for an execution group.
Does anyone know in the above 2 cases, only mqsireload is enough to help or do we need to go through whole BROKER re-start?
Thanks. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Jul 18, 2010 5:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you tried to use mqsireload for the execution group to pick up the new properties and how does that work out for you? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Sun Jul 18, 2010 5:48 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
fjb_saper wrote:
| Quote: |
| Have you tried to use mqsireload for the execution group to pick up the new properties and how does that work out for you? |
Well, the problem is it is very tough to know whether the below command has taken into affect, so if I reload the execution group I will always be in doubt whether the commands has really run or not.
mqsichangeproperties BRKBRK1 -e eg1 -o ComIbmSocketConnectionManager -n tcpNoDelay -v true
_________________
"For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Jul 18, 2010 6:22 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
you have naturally done a corresponding mqsireportproperties after your mqsichangeproperties ?
.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Jul 18, 2010 6:29 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Trust the IBM documentation.
Also consider upgrading to WMB 7 where more things can be set at the Execution Group level with mqsireload verus a full Broker restart. I hope Hursley continues to make more and more things available without a Broker or QM restart. A QM or Broker restart in the real world is not as easy as it is in the lab!
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Jul 18, 2010 8:15 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Good point Peter.
Then there are the 'User Defined Configurable Services' in 7.0.0.1.
Perhaps we can say good bye to bar files overrides at last!
It is a pity that is it not easy to ask broker to list out all the configurable service values (or all types) for an EG in one command.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Sun Jul 18, 2010 5:16 pm Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
smdavies wrote:
| Quote: |
| you have naturally done a corresponding mqsireportproperties after your mqsichangeproperties ? |
mqsireportproperties shows me that the value has changed, but has it really changed or waiting for broker to re-start? (Also note that changed properties value are visible immediately after the command and even there is no need to reload the execution group also) ..Something fishy? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Jul 18, 2010 5:45 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
And what happens when you run a test designed to validate that mqsireportproperties is accurate or not?
Or are you just willing to take the word of random, verbose, strangers on the internet? Wouldn't you much rather back that up with some of your own science? |
|
| Back to top |
|
|
| Rahul999 |
| Posted: Sun Jul 18, 2010 6:23 pm Post subject: |
|
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
mqjeff wrote:
| Quote: |
| And what happens when you run a test designed to validate that mqsireportproperties is accurate or not? |
Jeff, I did test one of the properties (after only reloading the execution group) and it worked fine. that's why the doubt came across, whether reloading is enough for all of the properties.
_________________
"For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Jul 18, 2010 7:50 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
|
|
