| Author |
Message
|
| coolestcapri15 |
 Posted: Mon Jan 07, 2008 11:50 am Post subject: Trigger monitor service in Windows for MQ v6.0 |
 |
|
Newbie
Joined: 07 Jan 2008
Posts: 5
|
Hello
I am using WebSphere MQ 6.0 with patch level CSD01. While creating the trigger monitor service in WIndows , what does the two options given in the 'Service Type' filed mean. I looked up on the IBM website and it instructs to select the 'command type' but doesnt explain why or what it means. Can someone explain whats the difference and what each one means.
Thanks in advance. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jan 07, 2008 11:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It seems pretty clear here:
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaj.doc/sc11270_.htm
| Quote: |
SERVTYPE
Specifies the mode in which the service is to run:
COMMAND
A command service object. Multiple instances of a command service object can be executed concurrently. You cannot monitor the status of command service objects.
SERVER
A server service object. Only one instance of a server service object can be executed at a time. The status of server service objects can be monitored using the DISPLAY SVSTATUS command. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| coolestcapri15 |
| Posted: Mon Jan 07, 2008 12:07 pm Post subject: |
|
|
Newbie
Joined: 07 Jan 2008
Posts: 5
|
Thanks for the link, maybe I over looked that. I am having issues with the service. MQ was migrated on the box from 5.3 to 6.0 and the trigger monitor service was automatically configured as a service after the upgrade. But only the start arguments were populated and the stop args filed was left blank. So when I stopped the qmgr, the service didnot stop and I could only stop it by using the PID from the task manager.
I thought by selecting the SERVTYPE to COMMAND we maybe able to fix that but from the explanation, looks like it will not make any difference.
Is there a way to fix that, or a better way to stop it, since we cannot see all the PIDs unless we have admin access on the server. Usually we login using the terminal services. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 07, 2008 12:13 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
runmqtrm should finish when the qmgr ends, I thought.
Edit: Unless the triggered application is a) being started "in the foreground", and thus the trigger monitor is waiting for it to end AND b) the triggered application is NOT using FAIL_ON_QUIESCE.
I.e. it's likely the problem is not with the trigger monitor service, but the triggered application or the process configuration.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| coolestcapri15 |
| Posted: Mon Jan 07, 2008 12:24 pm Post subject: |
|
|
Newbie
Joined: 07 Jan 2008
Posts: 5
|
jefflowrey
I am not sure if I understood your reply correctly. I noticed that this issue had nothing to do with the process being triggered. I tired this when there were no process definitions for the qmgr. This issue was not present obviously in new installation as we give the stop and start args during the service creation. I just didnt understand why MQ6.0 upgrade process fills in the start agrs but not the stop args.
My migration steps are:
1. On a box with MQ 5.3, CSD12, stop all qmgrs.
2. Stop IBM MQ service from My Computer -> Manage -> Services.
3. Put the CD for MQ6.0, select upgrade option, after installtion completes, bring all the qmgrs up.
4. I noticed then that the trigger monitor service is already configured under the services.
Hope this gives a clear understanding of the issue I am facing.
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 07, 2008 12:49 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay...
So, the trigger monitor service is already configured, and it has a start command...
But you said " I stopped the qmgr, the service didnot stop ".
I assume you mean the trigger monitor service, yes?
I am guessing that the start command is something to do with "runmqtrm", yes?
Runmqtrm should exit when it notices that the queue manager is started, so it shouldn't fail to stop when the queue manager stops.
So I'm confused about what it is that won't stop...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| coolestcapri15 |
| Posted: Mon Jan 07, 2008 1:21 pm Post subject: |
|
|
Newbie
Joined: 07 Jan 2008
Posts: 5
|
Yes it is the triggermonitor service I am talking about, and it is this service that wont stop when qmgr is stopped.
Here is the screenshot of the triggermonitor service properties for better understanding. This service was created while MQ5.3 was installed on the server and on migration to 6.0 this was converted to MQ service, as you can see the 'Stop command' and 'Stop args' have not been populated whereas start args have been. This makes the trigger monitor not to stop even though the qmgr is stopped. And so to forcefully kill it we are having to get admin access to the box to see the PID.
Thanks[/img] |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 07, 2008 1:27 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The exact same service configuration works just fine for me.
Are you sure you don't have any processes being triggered?
Are you running at a fairly recent revision of v6 - 6.0.2.2 or etc?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| UglyAngelX |
| Posted: Tue Jan 08, 2008 4:59 am Post subject: |
|
|
Voyager
Joined: 04 Dec 2001
Posts: 90
Location: BEARS FAN IN STEELER COUNTRY
|
| I think in the first post you were saying you were on MQ V6 CSD01 so I am thinking MQV6.0.2.1 we had issues with triggering with that version and went with V6.0.2.2 and the issues cleared up. |
|
| Back to top |
|
|
| coolestcapri15 |
| Posted: Tue Jan 08, 2008 8:12 am Post subject: |
|
|
Newbie
Joined: 07 Jan 2008
Posts: 5
|
Thanks for your responses. I am using MQ v 6.0.1.0. As you suggested, I might try installing the latest patch and see if that works. Also, do we need to change the service after the patch installation or will it automatically fix the issue?
Thanks |
|
| Back to top |
|
|
| UglyAngelX |
| Posted: Tue Jan 08, 2008 10:04 am Post subject: |
|
|
Voyager
Joined: 04 Dec 2001
Posts: 90
Location: BEARS FAN IN STEELER COUNTRY
|
| We did not need to change anything after going to 6.0.2.2 |
|
| Back to top |
|
|
|
|
