|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Alter QManager TRIGINT attribute takes effect immediately? |
« View previous topic :: View next topic » |
Author |
Message
|
KAKOZ |
Posted: Fri Mar 19, 2004 7:45 am Post subject: Alter QManager TRIGINT attribute takes effect immediately? |
|
|
Voyager
Joined: 26 Jan 2004 Posts: 90 Location: FRANCE
|
Hi,
I wonder if after having modified the value for TRIGINT for the queue manager this value has an immediate effect on the trigger mecanism ?
or do we have to stop/start the queue manager for the new value be taken?
Jack |
|
Back to top |
|
 |
kman |
Posted: Mon Mar 22, 2004 12:00 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003 Posts: 309 Location: Kuala Lumpur, Malaysia
|
normally queue manager changes does not take effect, until a refresh, or restart. but I maybe wrong on this.. will have to check |
|
Back to top |
|
 |
kman |
Posted: Mon Mar 22, 2004 12:09 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003 Posts: 309 Location: Kuala Lumpur, Malaysia
|
I check with the command reference, and it was not specific on restart, except with CCSID, so I take it, you don't have to restart. Meaning, effect is on the fly. |
|
Back to top |
|
 |
tkane |
Posted: Mon Mar 22, 2004 10:11 am Post subject: |
|
|
 Voyager
Joined: 23 Dec 2002 Posts: 82 Location: Kansas City
|
I've seen it take effect immediately on zOS.
I had one application using the batch trigger monitor that we would call il-behaved. It wasn't following the general rules and when I changed trigint from 999999999 to 60000 it generated lots of jobs that our application monitoring group complained about. I altered it back and they were ok. But on 49 of our 50 zOS queue managers we changed trigint on the fly from a high valule to a low without problems. On the 50th we changed back on the fly to a high value and the problem went away.
Haven't tried on the distributed platform though.
Good Luck
Tom |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Mar 22, 2004 2:34 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Quote: |
On the 50th we changed back on the fly to a high value and the problem went away.
|
Tom, sounds to me more like "we changed it back on the fly to a high value and the problem went back to being masked."
Trigger Interval of 60000 will never cause a problem, but will expose an app that can't handle one message a minute. _________________ 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
|
|
|
|