| Author |
Message
|
| angka |
 Posted: Tue Nov 21, 2006 1:38 am Post subject: Trigger Monitor |
 |
|
Chevalier
Joined: 20 Sep 2005
Posts: 406
|
Hi,
I set the trigger monitor on using services with the 'service control' field set as Queue manager 'start command' field as D:\dir\runmqtrm.exe and the 'start args' field as -m Qmgr -q InitQ
then i restart my queue manager. from InitQ queue status the 'handle state' field show Active. However when i put a message into the queue which i am monitoring, it throws a message into InitQ but somehow the trigger monitor did not pick up the message from the InitQ. and from the InitQ queue status, the 'Handle state' become Inactive.
But when i start the trigger monitor manually using command prompt the whole process works. btw I am working on Windows platform. Where does the problem lies? Thanks |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Nov 21, 2006 2:24 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
I suspect your initQ is not perfoming properly,
One question are you using System default initq ie: SYSTEM.DEFAULT.INITIATION.QUEUE or not.
and you stated that when you execute it manually its working fine.
I request you to go through the following site, i hope it will help you out in some extend.
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzal.doc/trgmons.htm
and please let us know the status
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| xxx |
| Posted: Tue Nov 21, 2006 8:48 pm Post subject: |
|
|
Centurion
Joined: 13 Oct 2003
Posts: 137
|
Problem may likely be in
1) PATH ( command prompt may have differnt path )
2) the userid you are running the application and the services which you started with |
|
| Back to top |
|
|
| angka |
| Posted: Tue Nov 21, 2006 10:19 pm Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005
Posts: 406
|
Hi,
Gaya3: my InitQ is a local queue i create but i used the attributes of SYSTEM.DEFAULT.INITIATION.QUEUE.
xxx: I did suspect it is due to the userid tt is causing the problem.. ya using command prompt and using services the userid is different but i added the same group to the services userid compare to the command prompt userid it still don't work. =( how to do set the path to be the same?
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 22, 2006 2:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Change your start command to redirect stdout and stderr to a file.
See what the file says when you run the trigger monitor as the other user.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| angka |
| Posted: Wed Nov 22, 2006 8:09 pm Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005
Posts: 406
|
Hi,
Jefflowrey: I tried using the stdOut and StdErr but nothing printed. and when i stop the Qmgr, the runmqtrm.exe process is not killed. i need to manually stop it before i can restart the Qmgr.. Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 23, 2006 5:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Log onto the machine as the service user, and try running the command manually and see what happens.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| angka |
| Posted: Sun Nov 26, 2006 11:51 pm Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005
Posts: 406
|
Hi,
Jefflowrey: I tried it out and it works.. no error.. looking at the status of the queue, it is the same service user which gave error.. I tried using the services for this user it won't work either. Thanks. |
|
| Back to top |
|
|
| KenD |
| Posted: Thu Nov 30, 2006 5:17 am Post subject: |
|
|
Newbie
Joined: 12 Oct 2005
Posts: 1
Location: Norway
|
Hi.
I'm having the same problem. If you have solved it, please post solution.
Ken |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 30, 2006 5:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Ken -
You're probably having a different problem than angka.
Angka -
If it works from a command prompt as the service user, but it doesn't work from the MQ service start, then it's probably a PATH or other environment problem.
If you start the MQ service while you're logged in as the service user, you *should* see the command prompt open up.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Nov 30, 2006 7:33 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Well, you might want to try supportpac MA7K, which is a trigger monitor that is designed to run as a windows service and can write lots of diagnostic info into the Windows event log. It can run as either an MQ client or server.
_________________
-wayne |
|
| Back to top |
|
|
| angka |
| Posted: Thu Dec 07, 2006 7:28 pm Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005
Posts: 406
|
Hi,
KenD: My problem not solved yet.
Jefflowrey: The command prompt din open up when i signed in as service user. Wat shld I path??
Wschutz: I will try it out..
Thanks.. |
|
| Back to top |
|
|
|
|
