| Author |
Message
|
| donbirno |
 Posted: Wed Jul 04, 2018 3:36 am Post subject: Trigger monitor stops working randomly in windows |
 |
|
Novice
Joined: 01 Nov 2013
Posts: 13
|
I have an issue with our PROD MQ.
MQ trigger monitor was working fine for over an year.
Issue started last month and occurred 3 time in a month, During issue I see runmqtrm.exe process is running but messages were not processed.
When I kill the process and start the process back messages are processed.
I monitored both MQ and server end nothing no abnormalities were noted.
What are the possible scenarios for this occurrence?
Trigger event is set to Every. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Jul 04, 2018 4:32 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Do you mean that Trigger Tyoe is set to EVERY on the application queue? Which Was set? TRIGGER or NOTRIGGER on the app queue?
When this occurs, what is the depth of the initiation queue? What is max depth of the initiation queue?
The trigger moniter writes informational messages to stdout about normal and abnormal events. What were the last 20 or so?
_________________
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 |
|
|
| donbirno |
| Posted: Wed Jul 04, 2018 6:06 pm Post subject: |
|
|
Novice
Joined: 01 Nov 2013
Posts: 13
|
Yes Trigger type is every, application queue set as TRIGGER(please note it was working good over an year without any issue).
depth of the initiation queue-110.
What is max depth of the initiation queue - default, 5000.
stdout ?? How to check it? |
|
| Back to top |
|
|
| hughson |
| Posted: Wed Jul 04, 2018 11:19 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
Is it possible that the trigger monitor is running triggered applications in line instead of as background tasks and that some long running application was triggered?
What was new 3 months ago? Did a new queue get set up for triggering? Review all your triggered queues to ensure they are correctly configured - e.g. how the application is run. Is the newest created queue different from all the other triggered queues in some way?
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jul 05, 2018 6:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I’d suggest that you modify the runmqtrm command that starts your trigger monitor to redirect stdout to a file. Something like:
runmqtrm -m qmgrname -q initqueuename >> runmqtrm.out
Next failure, look for ‘evidence’ in the runmqtrm.out file.
_________________
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 |
|
|
| gbaddeley |
| Posted: Sun Jul 08, 2018 3:47 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| hughson wrote: |
| Is it possible that the trigger monitor is running triggered applications in line instead of as background tasks and that some long running application was triggered? |
Yes, this can prevent the trigger monitor from processing trigger messages in a timely manner.
@Donbirno, Is the depth increasing on the initiation queue? Is ipprocs = 1 ?
Is your trigger monitor set up something like this:
| Code: |
define service('TRIGGER.MONITOR') replace
control(qmgr) servtype(server) descr('Trigger Monitor') +
startcmd('+MQ_INSTALL_PATH+bin\runmqtrm.exe') +
startarg('-m +QMNAME+ -q %TRIGMONINITQ%') +
stopcmd('+MQ_INSTALL_PATH+bin\amqsstop.exe') +
stoparg('-m +QMNAME+ -p +MQ_SERVER_PID+') +
stdout('%TRIGMONDATADIR%\stdout.log') +
stderr('%TRIGMONDATADIR%\stderr.log')
start service('TRIGGER.MONITOR') |
_________________
Glenn |
|
| Back to top |
|
|
|
|
