| Author |
Message
|
| mnance |
 Posted: Thu Jun 03, 2004 10:18 am Post subject: Trigger monitor |
 |
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
I have a Trigger Monitor that is setup to run as a service. All works well under Windows NT 4.0 sp6a. Once the server is upgraded to Windows Server 2003 it stops working. The service shows as Running but the runmqtrm.exe process is not running. When messages reach the queue they are not being processed. Trigger Depth is set for FIRST so it should process the messages once the first message hits the queue. If I stop/start the service everything is fine. However, I have over 800 servers that will need this action once they are upgraded. Has anyone heard of this problem or have any suggestions???
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
 |
| offshore |
| Posted: Thu Jun 03, 2004 11:37 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
mnance,
I think we all need some more information. What version of MQ and what CSD level. Also, when you say service are you running it as a MQ Service or did you set up a "NT" service? |
|
| Back to top |
|
|
| mnance |
| Posted: Thu Jun 03, 2004 11:41 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
Sorry about that. WebMQ 5.3 CSD04. The service is set up as an NT Service.
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jun 03, 2004 4:51 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Are you using the MA7K Support Pack to provide the Triger Monitor as a Windows Service?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| offshore |
| Posted: Fri Jun 04, 2004 3:17 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
Peter, I thought the MA7K was the client trigger support pac to run as a NT service.
Mnance mentioned that the runmqtrm.exe wasn't showing. Isn't the MA7K runmqtmc.exe???
Mnance, did you use the Windows resource kit to create a new service and have RUNMQTRM start? I think your best bet would to let MQ Series handle that service.
If you open the MQ Series services there is an option to add a new Trigger Monitor service. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jun 04, 2004 4:11 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
ma7k is known primarily for work with Client Trigger Monitors. But if you read the documentation that comes with it, it tells you how to run it with the regular TM as well.
You have a lot more options going this route, since the config file for the support pac has many parameters.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mnance |
| Posted: Fri Jun 04, 2004 4:19 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
I used a utility called instsrv.exe to install the NT service. The only problem with using MQ Explorer to create the Trigger Monitor is that I need the application that is being triggered to run under the account that the service running under, otherwise, it would not have the appropriate access.
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| mnance |
| Posted: Tue Jun 08, 2004 12:10 pm Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
I have noticed that after a reboot the NT service that I created using instsrv.exe and srvany.exe starts fine. However, it does not kick off the runmqtrm.exe process. I must stop/start the service in order to initialize the trigger monitor process. I have the service set up so that it depends on the MQSeriesServices service. So I know that MQ starts up before the new NT service.
Command used to create the service:
Instsrv IBDMQTRIG C:\Tech\srvany.exe
Ini File for Service
\Registry\Machine
System
CurrentControlSet
Services
IBDMQTRIG
Parameters
\Registry\Machine
System
CurrentControlSet
Services
IBDMQTRIG
Parameters
Application = REG_SZ C:\MQM\bin\runmqtrm.exe
\Registry\Machine
System
CurrentControlSet
Services
IBDMQTRIG
Parameters
AppParameters = REG_SZ -q Qname.INITQ
\Registry\Machine
System
CurrentControlSet
Services
IBDMQTRIG
DependOnGroup = REG_MULTI_SZ
\Registry\Machine
System
CurrentControlSet
Services
IBDMQTRIG
DependOnService = REG_SZ MQSeriesServices
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Jun 09, 2004 12:25 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Change the service to run a batch pgm. In the batch pgm, do something like:
echo %time% >> c:\temp\log.out
C:\MQM\bin\runmqtrm.exe -q Qname.INITQ >> c:\log.out 2>&1
(Note the 2>&1 as well!)
What happens on reboot now? What is listed in the file c:\log.out? |
|
| Back to top |
|
|
| mnance |
| Posted: Wed Jun 09, 2004 4:29 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
This is in the log file:
WebSphere MQ trigger monitor started.
Waiting for a trigger message
However, the runmqtrm.exe does not show up in task manager as a separate process. Before, the runmqtrm.exe was running in task manager under the user account specified by the service. Is that supposed to be the way it works?
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Jun 09, 2004 5:06 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
In task manager, do you have, (and if so tick!) the box saying show processes for all users. My bet is because 2003 supports terminal services, you are only seeing a portion of the processes in the task list.
Alternatively use something like process explorer (www.sysinternals.com) to list the processes.
If you can see it, add to the columns the userid column, and what userid is it running under?
However, the log implies it does get up and running, so are you certain that a trigger message gets generated, and that something is expected to be done? |
|
| Back to top |
|
|
| mnance |
| Posted: Wed Jun 09, 2004 5:10 am Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
I have "show processes for all users" checked as well as the USERID column selected. It does not show up.
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 09, 2004 5:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Do you see an instance of cmd.exe or command.exe for the batch file, running for the user in question?
Try changing the batch file by adding 'start' before the runmqtrm command.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Jun 09, 2004 5:21 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| My guess is that the trigger monitor is terminating for some reason, but take a trace and email it to me (instructions sent via PM) and I'll take a look... |
|
| Back to top |
|
|
| mnance |
| Posted: Wed Jun 09, 2004 12:30 pm Post subject: |
|
|
Apprentice
Joined: 15 Aug 2002
Posts: 44
|
Back to the original way that I setup the service:
In the registry under the service I have:
AppDirectory: Path
Application: C:\mqm\bin\runmqtrm.exe
AppParameters: -q QName.INITQ
Once the server reboots the service starts up automatically but doesnt spawn the runmqtrm.exe process under the user account specified. I can then stop/start the service and all works fine....including the messages being processed on the queue. I guess this is really an O/S problem with using Srvany.exe to run the application as a service and not so much MQSeries.
_________________
Salvation can only be achieved through Jesus Christ, our Lord and Saviour. |
|
| Back to top |
|
|
|
|
