| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trigger monitor |
« View previous topic :: View next topic » |
| Author |
Message
|
| masteringmq |
 Posted: Tue Dec 02, 2008 11:28 pm Post subject: Trigger monitor |
 |
|
Master
Joined: 20 Oct 2008
Posts: 200
|
| Today I imagine doing trigger monitor. It works. Then I imagine running two trigger monitor for a single initiation queue. However I did not see the impact. So if over a 1000 trigger messages are generated and put into the initiation queue, will having two trigger monitor running at the same time for a single initiation queue increase the performance (faster)?. The concept is to have one trigger monitor for one initiation queue. If a queue manager has more than 1 initiation queue, then I can run more than 1 trigger monitor, each serving an initiation queue. Please advice. |
|
| Back to top |
|
 |
| zpat |
| Posted: Wed Dec 03, 2008 12:25 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Triggering is suited for lower volume applications to avoid the continous execution of programs that are only needed some of the time.
If you are looking at high volumes, then use a number of long running applications which access the same input queue (MQGET with WAIT).
Adjust the number of threads/tasks until you achieve optimum throughput. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 03, 2008 1:14 am Post subject: Re: Trigger monitor |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| masteringmq wrote: |
| Today I imagine doing trigger monitor. |
You need to imagine less and read more.
| masteringmq wrote: |
| So if over a 1000 trigger messages are generated and put into the initiation queue |
If over a 1000 trigger messages are generated your design seriously needs work. That sort of situation is likely to crash your box; at best it's inefficient.
| masteringmq wrote: |
| The concept is to have one trigger monitor for one initiation queue. If a queue manager has more than 1 initiation queue, then I can run more than 1 trigger monitor, each serving an initiation queue. |
Yes. Why would you? This is like your 5 member cluster composed entirely of full repositories, which you claimed was a hub and spoke. At best it's an odd design, at worst it's unworkable.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 03, 2008 1:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
We're really not here to give you an advanced education in MQ design or implementation.
Please stop posting situations that you want explained to you. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 03, 2008 7:28 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Briefly:
Your question (imagining) leads to the need to balance triggering and applications doing MQGET with WAIT.
If an (poorly-written) application gets triggered on the arrival of a message in a triggered queue, gets the message, then ends itself, the application will need to be re-launched for every message that arrives. So, in your imagined scenario 1000 messages = 1000 launches of the application - each to consume one message. This is a (potential) huge waste of resources. I'd smack the programmer with whatever was nearby for writing such a program. Even if the specification called for only one message every hour, I'd construct the application with MQGET/WAIT in anticipation of the frequency of messages changing over time.
If your application anticipates more than one message in a given time-period, the application should MQGET with WAIT for the arrival of the first/next message(s). Much less resources are consumed by an application waiting for a message to arrive.
This is discussed in the WMQ Application Programming Guide. Read, research, experiment, as Mr. Jeff suggests.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
