| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| crtmqm -t Intervalvalue & TRIGINT qmgr attribute differe |
« View previous topic :: View next topic » |
| Author |
Message
|
| KAKEZ |
 Posted: Fri Oct 31, 2003 12:41 am Post subject: crtmqm -t Intervalvalue & TRIGINT qmgr attribute differe |
 |
|
Centurion
Joined: 10 Oct 2002
Posts: 117
|
Hi,
- have the crtmqm '-t IntervalValue' param and the qmgr TRIGINT attribute different meaning?
- the '-t IntervalValue' param for crtmqm not clear for me - if this param is important the crtmqm command is the only way to define it, if not we use the default which has a very large value!!!
thanks for advices
Jack |
|
| Back to top |
|
 |
| raj.in |
| Posted: Fri Oct 31, 2003 4:05 am Post subject: |
|
|
Novice
Joined: 15 Sep 2003
Posts: 10
Location: India
|
the parameter TRIGINT is used when we set the TRIGTYPE as FIRST, by default TRIGINT takes the default value which is 999 999 999 unless you specify while creating the QMGR with -t attribute set to a value between o to 999 999 999 .
this TRIGINT value ensures that the triggering is suspended after queue depth changes from 0 to 1 (ie, first message arrives on the queue),so that any message that comes within this specified interval of time will not generate another trigger message.
cheers:)
raj |
|
| Back to top |
|
|
| KAKEZ |
| Posted: Fri Oct 31, 2003 4:25 am Post subject: |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 117
|
thanks Raj,
that's right - these two values concern the same mqseries element - i have verified that creating a qmgr via crtmqm with a value 1000 and we find the same value inside the qmgr attribute TRIGINT once the qmgr has been created
cheers
Jack |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Nov 01, 2003 4:11 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
this TRIGINT value ensures that the triggering is suspended after queue depth changes from 0 to 1 (ie, first message arrives on the queue),so that any message that comes within this specified interval of time will not generate another trigger message.
|
This is not quite correct. The Trigger Interval tells the queue manager how often it should reset an interal switch when determining if a triggered on first queue should genereate another trigger message.
Triggered on first queues only cause the QM to generate a trigger message of the queue goes from 0 to 1. If for some reason the queue is at a depth higher than 0, any new messages arriving do not cause the depth to go from 0 to 1, so there are no more trigger messages.
If you set trigger interval to 5 minutes (300000), then every 5 minutes, the QM says to itself "OK, for all trigger on first queues, I dont care what the previous depth was. Any new messages that arrive on triggered on first queues from this point forward I will consider to be valid trigger events (as if the depth was going from 0 to 1)".
_________________
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
|
|
|
|
