Posted: Sat Aug 05, 2006 2:12 pm Post subject: triger type of first
Novice
Joined: 11 Jul 2006 Posts: 17 Location: USA
with trigger type of FIRST I notice sometimes that it does not trigger .
what could be the possible reasons .
I think its a timing issue where the triggered process is exiting after
dequeuing the messages and new message arrive at the queue so probably qmanager thinks that the process is still reading the queue
and does not trigger.
is it a good practise to set the TRIGGER INTERVAL attribute at qmanager
level but then it might start behaving like a trigger type of EVERY if
the trigger interval value is low.
is there any best practise for setting or not setting the trigger interval.
We have the trigger interval @ 00:05:00 i.e. 300000 ms
One thing you can do is to make sure the message triggering is available on the queue when the app starts. Do a get with wait and set the wait interval high enough (5 to 10 seconds) should be enough.
This will mean as well that your app will bridge the get wait interval and not trigger. You need to exit as soon as you get the last message (RC 2033 on get) so that there is no process servicing the queue in order to let the system trigger again.
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