| Author |
Message
|
| KramJ |
 Posted: Fri Jan 27, 2006 7:18 am Post subject: Application triggering stops on MQ client |
 |
|
Voyager
Joined: 09 Jan 2006
Posts: 80
Location: Atlanta
|
| We are having an issue with application triggering stopping on our MQ test client. Trigger monitors are still running but the application is not being triggered. The initiation queue starts filling with messages. I can stop the SVRCONN channel, kill the remaining trigger monitors on the client, clear the initiation queue, restart the channel and trigger monitors and the application starts triggering again. There are no errors in the logs on either client or queue manager and no FDCs. This has happened at CSD levels, 7, 11, and 12. Has anyone had a similar situation? |
|
| Back to top |
|
 |
| wschutz |
| Posted: Fri Jan 27, 2006 7:23 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Is the TM starting the application as a background task (ie, "start" for windows, "&" for unix)? If it isn't, then the TM can't start another application until the first one completes.
_________________
-wayne |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jan 28, 2006 10:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You might as well want to check the TRIGINT value for your qmgr.
We have it set to 5 min (300000)
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| KramJ |
| Posted: Mon Jan 30, 2006 5:40 am Post subject: |
|
|
Voyager
Joined: 09 Jan 2006
Posts: 80
Location: Atlanta
|
I checked the applications. There are starting in the background. I checked TRIGINT on the queue manager and it was set to 90. Wow, 90 milliseconds seems really low. I changed TRIGINT to 90000, the same as the QA and production queue managers that do not have the problem. I found an explanation of TRIGINT at: http://www-1.ibm.com/support/docview.wss?uid=swg21212328
Can you add some more info on the setting and how to determine the optimum one. Thanks. |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Jan 30, 2006 6:35 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Are you using TRIGTYPE=FIRST? TRIGINT only applies to FIRST.
I'd suggest running your trigger monitor itself in the foreground so you can see if any messages are being displayed that might help you figure out what the problem is.
_________________
-wayne |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jan 30, 2006 6:44 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It can be worth running the same application on a timed schedule as well as being triggered (assuming it can run without trigger data).
This gives you a failsafe mode if triggering fails and sometimes clearing the queue down will also reset the triggering.
The application should process the queue until empty in any case.
I also prefer to make the MQGET have a short GMO wait interval, just in case it gets triggered slightly before the message is actually available.
Finally have some system management alerting on queue depth to detect the triggering failure and initiate investigation.
Of course, it may simply be easier to have the application keep running all the time with MQGET WAIT. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 30, 2006 9:33 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| wschutz wrote: |
| Is the TM starting the application as a background task (ie, "start" for windows, "&" for unix)? If it isn't, then the TM can't start another application until the first one completes. |
I am willing to bet this is the problem. TRIGINT is a good thing to have set, but its not the issue here (if it was, he wouldn't have seen the INIT q filling up with trigger messages).
The problem is not the generation of trigger messages, but why the trigger monitor is not consuming them. The manuals are very good on when trigger messages are produced by the QM, and very vague as to when the trigger monitor actually consumes them.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| KramJ |
| Posted: Thu Feb 02, 2006 7:59 am Post subject: |
|
|
Voyager
Joined: 09 Jan 2006
Posts: 80
Location: Atlanta
|
| I think this is a problem with the application. The last time it happened I found some specific errors in the application's log file and notified the application developers. They were able to fix the problem without me having to run through the sequence of stopping triggering, clearing the initq, etc. I haven't heard back from the yet as to what they did. |
|
| Back to top |
|
|
|
|
