| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TRIGGER CHANGING TO NOTRIGGER |
« View previous topic :: View next topic » |
| Author |
Message
|
| pan_khandar |
 Posted: Tue Jun 25, 2002 6:10 am Post subject: TRIGGER CHANGING TO NOTRIGGER |
 |
|
Novice
Joined: 21 Jun 2002
Posts: 17
|
 Please help me here ..
I created a queue using TRIGGER, TRIGTYPE(DEPTH) TRIGDPTH(2) options. Wheneven i send two messages trigger activate but queue changed to NOTRIGGER.
Thanks in advance ... |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Tue Jun 25, 2002 7:36 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
what happens if you read those 2 messages and then send 2 more, alot of the
Queue properties are changed back and forth by MQSeries, IE if you
stop a sender channel, then go look at the GET properity you will find it set ot dsabled. Start the channel and get will get set to ENABLED by the
QMGR.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jun 25, 2002 8:15 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Queues that are triggered on depth will be changed to NoTrigger when the trigger actually goes off. It is then up to the application to set triggering back on by using the MQSET call.
See the Application Programming Guide's section on triggering for more details.
This turning of the trigger to off only happens like this for Depth, NOT First or Every.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| pan_khandar |
| Posted: Tue Jun 25, 2002 8:17 am Post subject: Still not get it |
|
|
Novice
Joined: 21 Jun 2002
Posts: 17
|
Hi,
i still don't understand..
Can you tell me how to stop changing queue property from TRIGGER to NOTRIGGER after every message set ??
Thanks
pankaj
---------------------------------------------------- |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Jun 25, 2002 9:04 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Pankaj,
As you know, there are several different types of triggers. You can trigger on FIRST, EVERY, and DEPTH. If you trigger on FIRST or EVERY, the TRIGGER property will always stay set. However, if you trigger on DEPTH, the moment the trigger fires, the queue's property changes from TRIGGER to NOTRIGGER.
Why does it do this? Well, imagine you want the queue to trigger after the depth reaches 10. You do this because you send messages in logical groups of 10 let's say. If the depth goes to 10, your application gets triggered, and it starts removing messages from the queue. But let's say that the queue stays set to TRIGGER. Your application removes one message, now there's 9 on the queue. But guess what, another batch of messages start coming in. Well, the first message that comes will cause the depth to go to 10, and another trigger will happen, and a second copy of your application will be launched - but the second group of 10 hasn't even arrived yet!
So, the answer is for the queue manager to automatically turn the queue to NOTRIGGER once the depth trigger is fired. This way, it's up to your application to do whatever is necessary to get the queue back into its initial state, set the queue back to TRIGGER, and exit.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| pan_khandar |
| Posted: Tue Jun 25, 2002 9:18 am Post subject: |
|
|
Novice
Joined: 21 Jun 2002
Posts: 17
|
Brandon
Thank you very much ... I got it ...
Thanks & Reagrds
Pankaj
----------------------------------------------------------- |
|
| 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
|
|
|
|
