| Author |
Message
|
| vam |
 Posted: Thu Nov 04, 2010 11:03 am Post subject: Trigger_Monitor_Service Not working properly |
 |
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
Hello MQSeries Team,
we are having issues with trigger monitor service which is not working properly. Steps to create triggering process are all being correct.Doulbled Checked it.
So I tried to restart it (stopped it) graphically(Windows) ......but it is not getting stopped and so obviously no option to change.
I had tried to do it using command prompt.
-------------------------------------------------------------------------------------
STOP SERVICE(TRIGGER)
2 : STOP SERVICE(TRIGGER)
AMQ8739: Stop cannot be executed for service with blank STOPCMD.
START SERVICE(TRIGGER)
3 : START SERVICE(TRIGGER)
AMQ8737: Service already active.
-------------------------------------------------------------------------------------
QMGR LOG:
Process(7044.1) User( Program(amqzmgr0.exe)
AMQ5042: Request to start SERVICE - TRIGGER failed.
EXPLANATION:
The request to start the process SERVICE - TRIGGER failed.
ACTION:
Consult the Queue Manager error logs for further details on the cause of the
failure.
_____________________________________________________________
SYSTEM MQ Error LOG:
Process(50328.97270) User(tom) Program(javaw.exe)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier CBF. This message is issued in
association with other messages.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the WMQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 777 --------------------------------------------------------
Process(50328.97270) User(tom) Program(javaw.exe)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 50328.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the WMQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 821 --------------------------------------------------------
Process(50328.97294) User(tom) Program(javaw.exe)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier CB3. This message is issued in
association with other messages.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the WMQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 777 --------------------------------------------------------
Process(50328.97294) User(tom) Program(javaw.exe)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 50328.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the WMQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
------------------------------------------------------
FDC FILE:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu November 04 2010 13:52:32 Eastern Daylight Time |
| UTC Time :- 1288893152.643000 |
| UTC Time Offset :- 60 (Eastern Daylight Time) |
| Host Name :- WLQTSO2 |
| Operating System :- Windows Server 2003, Build 3790: SP1 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.0.1 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- UN514000 |
| Application Name :- MQM |
| Component :- DmQueueManager.onError |
| SCCS Info :- eclipse/common/amqjxtra.c, 1.22.1.1 |
| Line Number :- 610 |
| Build Date :- Jan 15 2009 |
| CMVC level :- p700-001-090115 |
| Build Type :- IKAP - (Production) |
| UserID :- TOM |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\java\jre\bin\jav |
| aw.exe |
| Addressing mode :- 32-bit |
| Process :- 00050328 |
| Thread :- 00097270 |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- MQRCCF_NO_STOP_CMD |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Comment1 :- MQJE001: Completion Code '1', Reason '3263'. |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu November 04 2010 14:04:54 Eastern Daylight Time |
| UTC Time :- 1288893894.137000 |
| UTC Time Offset :- 60 (Eastern Daylight Time) |
| Host Name :- WLQTSO2 |
| Operating System :- Windows Server 2003, Build 3790: SP1 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.0.1 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- UN514000 |
| Application Name :- MQM |
| Component :- DmQueueManager.onError |
| SCCS Info :- eclipse/common/amqjxtra.c, 1.22.1.1 |
| Line Number :- 610 |
| Build Date :- Jan 15 2009 |
| CMVC level :- p700-001-090115 |
| Build Type :- IKAP - (Production) |
| UserID :- TOM |
| Process Name :- D:\Program Files\IBM\WebSphere MQ\java\jre\bin\jav |
| aw.exe |
| Addressing mode :- 32-bit |
| Process :- 00052288 |
| Thread :- 00000049 |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- MQRCCF_SERVICE_RUNNING |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Comment1 :- MQJE001: Completion Code '1', Reason '3251'. |
| |
| |
+-----------------------------------------------------------------------------+
Please need your inputs to resolve it. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Nov 04, 2010 11:12 am Post subject: Re: Trigger_Monitor_Service Not working properly |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vam wrote: |
| we are having issues with trigger monitor service which is not working properly. |
| vam wrote: |
| Process(50328.97270) User(tom) Program(javaw.exe) |
Since when has the trigger monitor (runmqtrm) been a Java application? Running under a user called tom?
Or do you mean something other than the IBM-supplied trigger monitor?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 04, 2010 11:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Please show the output of
DISPLAY SERVICE(TRIGGER) ALL
using [ c o d e ] [ / c o d e ] tags, please. |
|
| Back to top |
|
|
| vam |
| Posted: Thu Nov 04, 2010 11:53 am Post subject: Trigger_Monitor_Service Not working properly |
|
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
DISPLAY SERVICE(TRIGGER) ALL
1 : DISPLAY SERVICE(TRIGGER) ALL
AMQ8629: Display service information details.
SERVICE(TRIGGER) CONTROL(STARTONLY)
SERVTYPE(SERVER) STARTCMD(runmqtrm)
STARTARG(-m MCK.PMQ.KI -q MCK.PMQ.KI.INITIATION QUEUE)
STOPCMD( ) STOPARG( )
STDOUT( ) STDERR( )
DESCR(Trigger monitor) ALTDATE(2009-08-13)
ALTTIME(14.44.16) |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 04, 2010 12:00 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So the runmqtrm process is not javaw.exe, nor will it be executed as the user TOM from that service.
You should
ALTER SERVICE(TRIGGER) STDOUT('C:\temp\triggermonitor.txt') then START SERVICE
and examine the trigermonitor.txt file. |
|
| Back to top |
|
|
| vam |
| Posted: Thu Nov 04, 2010 12:19 pm Post subject: Trigger_Monitor_Service Not working properly |
|
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
I had done as suggested by you and tried to start service,It's still showing as stopping and not being stopped from long time and again i am getting the same message.
STOP SERVICE(TRIGGER)
2 : STOP SERVICE(TRIGGER)
AMQ8739: Stop cannot be executed for service with blank STOPCMD.
START SERVICE(TRIGGER)
3 : START SERVICE(TRIGGER)
AMQ8737: Service already active.
* It didn't write any thing in the 'triggermonitor.txt' file
my user name is (TOM) and I tried to start the service ......so it showed my name in the error logs and fdc files. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 04, 2010 12:25 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If it's not stopped, then you will need to end the runmqtrm process manually.
You probably want to capture the stderr as well as the stdout.
So you used MQExplorer to try and stop things, which is why it shows the javaw.exe and the TOM userid. But those are errors within MQ explorer, not errors about runmqtrm. |
|
| Back to top |
|
|
| vam |
| Posted: Thu Nov 04, 2010 12:43 pm Post subject: Trigger_Monitor_Service Not working properly |
|
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
I had tried to stop it using MQ Explorer.
Later I tried using command prompt also.........I hope it is manuall........or should I stop any process in task manager ? |
|
| Back to top |
|
|
| vam |
| Posted: Thu Nov 04, 2010 1:54 pm Post subject: Trigger_Monitor_Service Not working properly |
|
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
| I had done it manually(from Task Manager).It got stopped and later the trigger monitor service was fine and running.But the messages in the queue which got struck didn't get triggered. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Nov 04, 2010 11:13 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
maybe they got triggered but your application program is not processing them? did you check the output from the trigger monitor? or run the trigger monitor "manually" in the foreground and check if the trigger fires, if it does, then maybe its up to the application start or the application. sometimes trigger messages can be found in the DLQ if the application can not be started. whats that jawaw programm from the posts before? is that the application? make sure you meet the trigger conditions what does the mq logs say? if there are already messages in the queue. what are your trigger settings of the application queue? please show application queue definition and process definition.
so may things you can check, and so less information you provided.
i'd start with the trigger monitor anyway....... check you got a trigger message, then continue with application start and application message processing.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| vam |
| Posted: Wed Nov 10, 2010 10:37 am Post subject: Trigger_Monitor_Service Not working properly |
|
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
I our triggering we are using an utility which gets invoked when trigger condition matches and writes the messages from queue to file.
Now i had found the issue(mentioned in StdErr logfile) with that utility(QMF) as shown below:
'QMF'is not recognized as an internal or external command, operable program or batch file.
Is it a problem with classpath setting. |
|
| Back to top |
|
|
| pdmenon |
| Posted: Fri Feb 11, 2011 3:13 am Post subject: Re: Trigger_Monitor_Service Not working properly |
|
|
Voyager
Joined: 05 Apr 2010
Posts: 80
|
| vam wrote: |
DISPLAY SERVICE(TRIGGER) ALL
1 : DISPLAY SERVICE(TRIGGER) ALL
AMQ8629: Display service information details.
SERVICE(TRIGGER) CONTROL(STARTONLY)
SERVTYPE(SERVER) STARTCMD(runmqtrm)
STARTARG(-m MCK.PMQ.KI -q MCK.PMQ.KI.INITIATION QUEUE)
STOPCMD( ) STOPARG( )
STDOUT( ) STDERR( )
DESCR(Trigger monitor) ALTDATE(2009-08-13)
ALTTIME(14.44.16) |
Dear Vam,
Should trigger run only when qmgr is up?.. then you can try this..
ALTER SERVICE(TRIGGER) CONTROL(QMGR)
When you stop the qmgr, automatically "service" gets terminated.
Hope this helps.
 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 11, 2011 3:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you really want to stop the trigger monitor just try the following:
| Code: |
ALTER QL(MCK.PMQ.KI.INITIATION QUEUE) get(disabled)
ALTER QL(MCK.PMQ.KI.INITIATION QUEUE) get(enabled) |
Oh and of course don't forget to restart it after having redirected the output as mqjeff showed you... This will enable you to diagnose the problem.
Note that there is an exemple of the stop command for the trigger service somewhere in the infocenter but I believe it is linked to the qmgr stopping...
Setting the initq to get disabled will stop the trigger monitor without stopping the qmgr... Don't forget to get enable it right away afterwards...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Feb 15, 2011 1:25 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 15, 2011 4:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Read that ... I believe this is geared at terminating the service when the qmgr shuts down. Have never tried to run it manually to stop the service...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
