| Author |
Message
|
| franki99 |
 Posted: Thu May 04, 2006 9:26 pm Post subject: automatic start of an extra trigger monitor |
 |
|
Newbie
Joined: 04 May 2006
Posts: 5
|
Hello,
We experience the strange fact that when we have started an triggermonitor (runmqtrm) on the default initiation queue and something (we dont know what) goes wrong, the queuemanager (????) decides to start an extra triggermonitor. The problem is that after the start of the extra trigger monitor triggering DOESN'T work at all anymore.
We have to stop both trigger monitors and restart the only one we need.
Anyone experienced this also ?
By the way we use WMQ 5.3 on AIX.
Frank |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Thu May 04, 2006 11:36 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The qmgr does not start a trigger monitor; something in your system is doing it.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| franki99 |
| Posted: Thu May 04, 2006 11:43 pm Post subject: |
|
|
Newbie
Joined: 04 May 2006
Posts: 5
|
| That is true i guess, but why doesnt triggering work at all after the second trigger monitor is started? |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri May 05, 2006 1:26 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Why bother to try and find that out? Stop the second trigger monitor from being started, and you will not have the problem.
Fix the cause, not the symptom.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| franki99 |
| Posted: Fri May 05, 2006 1:45 am Post subject: |
|
|
Newbie
Joined: 04 May 2006
Posts: 5
|
| i cant explain, find or what ever why the second one is started, tips ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri May 05, 2006 2:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If on windows check your services and the service fault behavior.
It may specify restart.
The service may not be at fault but some time out condition may lead the service manager to believe that the service has died. If you have restart on "what to do on error" for the service that might be the cause...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| franki99 |
| Posted: Fri May 05, 2006 3:08 am Post subject: |
|
|
Newbie
Joined: 04 May 2006
Posts: 5
|
|
| Back to top |
|
|
| jlamond |
| Posted: Fri May 05, 2006 5:07 am Post subject: |
|
|
Voyager
Joined: 28 May 2002
Posts: 94
Location: Paris
|
This should not cause any problem. You may run as many trigger monitor as you want. This is actually the best way for parallel processing, since the runmqtrm / runmqtmc does not return before the end of the application program.
With MQ 5.3, you should be able to query who's connected to the initQ. You should also check that your initq as a default attribut of open shared.
Regards
_________________
Jean-Marc |
|
| Back to top |
|
|
| mvic |
| Posted: Fri May 05, 2006 5:22 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| jlamond wrote: |
| This should not cause any problem. You may run as many trigger monitor as you want. This is actually the best way for parallel processing, since the runmqtrm / runmqtmc does not return before the end of the application program. |
The MQ manuals appear to agree:
| Quote: |
The trigger monitor does not look to see if there is another message on the initiation queue until the completion of the application that it has just started. If the application has a lot of processing to do, the trigger monitor might not be able to keep up with the number of trigger messages arriving. You have two options:
* Have more trigger monitors running
* Run the started applications in the background
If you have more trigger monitors running, you can control the maximum number of applications that can run at any one time. If you run applications in the background, there is no restriction imposed by WebSphere MQ on the number of applications that can run. |
|
|
| Back to top |
|
|
| vennela |
| Posted: Fri May 05, 2006 8:09 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Interesting.
One of the MQ developers gave a very good reasoning for not running many trigger monitors.
Let's say you have 10 applications, so you will run 10 trigger monitors.
Instead, you could as well keep your apps polling instead of trigger monitor doing the polling.
I liked the reason, but what the manual says also makes sense. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 05, 2006 8:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If I have a "batch" process that runs once a day and produces 10,000 messages on a queue all at once, I would much rather use 10 trigger monitors than 10 listeners.
Among other things, I would not have to worry about memory leaks in in-house code.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| franki99 |
| Posted: Sun May 07, 2006 10:15 pm Post subject: |
|
|
Newbie
Joined: 04 May 2006
Posts: 5
|
| How can you query who's connected to the initQ ? |
|
| Back to top |
|
|
| jlamond |
| Posted: Mon May 08, 2006 12:23 am Post subject: |
|
|
Voyager
Joined: 28 May 2002
Posts: 94
Location: Paris
|
display qstatus(<queue name>) all type(quque) type(handle).
You may look at MQSC command reference for more detail.
If you use MMC you can right click on the initq and select "status".
That must be done while those process are connected.
Regards
_________________
Jean-Marc |
|
| Back to top |
|
|
|
|
