| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Service as Trigger monitor is not working |
« View previous topic :: View next topic » |
| Author |
Message
|
| bruce2359 |
 Posted: Mon Dec 22, 2014 7:03 am Post subject: |
 |
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
It seems odd that there is nothing in the AMQERR01.LOG for the qmgr for a Service failure.
It seems odd that there is no TRIGGER/NOTRIGGER attribute for the triggered application queue. Perhaps this is also a copy/paste failure.
It seems equally odd that CURDEPTH is zero for the triggered queue, the initiation queue, and the dead-letter queue.
Does the dead-letter queue exist? Does the qmgr know the name of the dead-letter queue?
_________________
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 |
|
 |
| mqjeff |
| Posted: Mon Dec 22, 2014 7:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If the trigger monitor could start up, but not launch the program, it would write errors to the stderr, or stdout, not throw a message into AMQERR01.LOG.
If NOTRIGGER was set, then the trigger monitor wouldn't work when run in the foreground.
CURDEPTH is presumable a point-in-time, rather than data from when the trigger monitor doesn't work. |
|
| Back to top |
|
|
| praveenmq |
| Posted: Mon Dec 22, 2014 9:42 am Post subject: |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
mqjeff has pointed out the exact scenarios.
Yes there is a system default DLQ assigned for the QMGR.
I am really confused why the trigger monitor service is running but not triggerring the application whereas if i run in cmd prompt normally using runmqtrm it runs perfectly.
Any suggestions to check the services?
_________________
Jack |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Dec 22, 2014 10:20 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Well, again, check that the queue manager user has permissions to execute the triggered program (not the trigger monitor). Check that the queue manager user has permission to access the directories that lead up to the triggered program.
Check that the queue manager user has access to write to the stdout and stderr files you have named in the service definition.
Check that there is no information in those files.
Check that runmqtrm is even starting up when you start the service. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Dec 22, 2014 11:03 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Please do these things as one test:
Start the Service, then check (with Windows Task Manager or Windows Process Explorer or equivalent) to see if the trigger monitor is running.
Next, put a message to the app queue; then, using the same tool, check to see if the triggered app comes to life.
Next, look for queue depth for the app queue, the initq, the dlq.
Look at the error log for this qmgr.
Look in the Windows Event Log.
_________________
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 |
|
|
|
|
|
|
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
|
|
|
|
