| Author |
Message
|
| vids |
 Posted: Thu Oct 16, 2003 10:13 am Post subject: Trigger Monitor issue |
 |
|
Acolyte
Joined: 24 Mar 2003
Posts: 68
Location: CA, USA
|
Hi all,
I have some issues with the trigger monitor.
At present I'm running a trigger monitor in a dev box using a batch file.
Command :
runmqtrm -m QM1 -q SYSTEM.DEFAULT.INITIATION.QUEUE
This is working absolutely fine. But I want to use Websphere MQ Services to run the trigger monitor.
When I use Services to run the trigger monitor, it's not working. Trigger will not be invoked.
I have given the same initiation queue SYSTEM.DEFAULT.INITIATION.QUEUE in the services. And before
running this, I stopped the trigger monitor which was already running in command prompt.
We have Windows 2000 and using Terminal Services Client to log on to the server. Is there any problem using Terminal services???
Thanks
Vij |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Thu Oct 16, 2003 10:21 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
You should be able to run it as a service through MQSevices without issue
are there any errors in the logs ????
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| vids |
| Posted: Thu Oct 16, 2003 7:13 pm Post subject: |
|
|
Acolyte
Joined: 24 Mar 2003
Posts: 68
Location: CA, USA
|
Jeff,
I don't see any errors in the log.
What I noticed is, When I put the first message to the triggered queue,
trigger is invoked and trigger monitor pulls the trigger message from the initiation queue but it doen't run the application specified in the process.
When I put the next message, I can see the trigger message in the SYSTEM.DEFAULT.INITIATION.QUEUE and it's not pulled by trigger monitor.
Looks like trigger monitor pulls the trigger message for the first time and it hangs.
I don't have this problem when I run the trigger monitor using runmqtrm in command prompt.
Thanks
Vij |
|
| Back to top |
|
|
| mrlinux |
| Posted: Fri Oct 17, 2003 4:48 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well it's either a env. variables or authority issue. There is always the possibilty of an MQSeries bug.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Oct 17, 2003 8:00 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
MUser_MQAdmin is not having proper previleges to run your application. Give it the authority and you will be able to run trigger monitor from MQ Services
_________________
-Ratan |
|
| Back to top |
|
|
| vids |
| Posted: Fri Oct 17, 2003 12:45 pm Post subject: |
|
|
Acolyte
Joined: 24 Mar 2003
Posts: 68
Location: CA, USA
|
Rathan,
You are right. It was an authority issue.
I have already solved that issue by giving the appropriate rights and it's working fine now.
Thanks
Vij
_________________
Vids |
|
| Back to top |
|
|
| bpcluser |
| Posted: Wed Oct 22, 2003 1:33 am Post subject: Trigger Monitor |
|
|
Newbie
Joined: 08 Oct 2003
Posts: 1
|
Rathan/Vij
I too faced the same problem of trigger monitor,
will u please tell me, what are appropriate rights to be given this user?
pls. help me....
Siva |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed Oct 22, 2003 9:27 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
what ever is needed to execute a program.
_________________
-Ratan |
|
| Back to top |
|
|
|
|
