Posted: Fri Jun 18, 2004 3:27 am Post subject: Triggermonitor
Novice
Joined: 19 Nov 2003 Posts: 14
Two questions for anyone who feels like answering.
Is it recommended to balance load, to have more than one triggermonitor active?
We often have situations where there are many queues filling up and MQ switches between queues to pick off a few messages from one queue before handling the next queue. I would prefer "simultaneous" receival of messages.
Suppose I define one local queue and two alias queues refering to the one local queue but with different priorities. Would messages that are put simultaneously on each alias queue, be processed in such a way that any message put on the alias queue with the highest priority will get processed before the ones already on the local queue with lower priority.
It's recommended (at least, by me ) that you code your process definitions so that they start a new process.
This means that the trigger monitor will read the initiation message, start a new process in response, and get the next initiation message without waiting for the triggered process to run or fail.
Running multiple copies of the same trigger monitor against the same initiation queue isn't a bad idea as long as you are sure that the trigger monitor can share the queue. Some of the supplied trigger monitors are also threadable and can run multiple listener threads. _________________ I am *not* the model of the modern major general.
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