| Author |
Message
|
| jared_hagel |
 Posted: Wed May 04, 2005 3:58 pm Post subject: MA7K - Trigger monitor service - Problem |
 |
|
Apprentice
Joined: 23 Jun 2004
Posts: 29
|
Hi guys,
I have a problem where the Client Trigger Monitor Windows Service (http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24000149&loc=en_US&cs=utf-8&lang=en) doesn't always close it's connection after it's restarted.
I'm using the monitor to monitor our initiation queue. After I start the monitor, the "Open Input Count" property of the queue changes from 0 to 1, as it should. After I shut down the monitor, the "Open Input Count" property of the initiation queue MAY return to 0 or it may stay at 1. The property returns to 0 if I run the client monitor on a Windows 2000 Professional machine, but will remain stuck at 1 if I run the client monitor on a Windows 2000 Advanced Server. Sigh... I suppose the problem might be that Windows 2000 Advanced Server isn't supported...
In the setup.ini file used to configure the monitor I use all default settings. The only custom setting I have is:
| Code: |
Thread:
TriggerQueueName=MQSVC.INITIATION
CONNAME=st2dotnet01v(2000)
CHANNEL=MQD45_SVRCONN
|
IBM doesn't provide support for this product either, right? I may be stuck building a client trigger monitor myself. O well. This problem occurs when the MQ Server is run on both UNIX and Windows 2000 Advanced Server machines.
Thanks,
Jared |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed May 04, 2005 4:06 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Have you enabled any of the automatic service restart features on the service configuration? (In the Windows Service mmc on the properties of the service itself - not in the INI).
If you can't get this service to work reliably, then just use Scheduled Tasks to run an instance or three of runmqtrmc.exe.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jared_hagel |
| Posted: Wed May 04, 2005 8:35 pm Post subject: |
|
|
Apprentice
Joined: 23 Jun 2004
Posts: 29
|
Thanks Jeff,
I think the automatic service restart feature is enabled by default in the Windows Services mmc for the monitor service. My problem is that after I stop the windows service, the Open Input Count of the initiation queue is the same as it was while the windows service was running. Turning off the windows service didn't decrease the Open Input Count of the initiation queue.
Hmm... Using runmqtrmc.exe might be worth a shot. Far better than making my own monitor. I'll look into it in the morning. In the WebSphere MQ Clients pdf, the only documented arguments are the queue manager & initiation queue. Does runmqtrmc.exe also accept the remote server name, connection channel name & port number?
Thanks,
Jared |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu May 05, 2005 3:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| jared_hagel wrote: |
| I think the automatic service restart feature is enabled by default in the Windows Services mmc for the monitor service. My problem is that after I stop the windows service, the Open Input Count of the initiation queue is the same as it was while the windows service was running. Turning off the windows service didn't decrease the Open Input Count of the initiation queue. |
My point was to make sure that it was actually stopped when you checked the IC.
| jared_hagel wrote: |
| Hmm... Using runmqtrmc.exe might be worth a shot. Far better than making my own monitor. I'll look into it in the morning. In the WebSphere MQ Clients pdf, the only documented arguments are the queue manager & initiation queue. Does runmqtrmc.exe also accept the remote server name, connection channel name & port number? |
No.
It uses the MQSERVER environment variable or the client conn table variables. So use a .BAT file to start runmqtrmc and set the appropriate info in there.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu May 05, 2005 5:26 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Is the triggered program run with START prepended. For example, your process def should like like this:
START C:\CIMS\CimFin\Triggers\FOCSphase2exec.exe
If not, the TM waits until the triggered program ends before it ends. If that triggered program is still running, so will the TM, even if you stop the service.
After you stop the service, look in task manager to see if either the TM or your triggered exe is still lurking.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jared_hagel |
| Posted: Fri May 13, 2005 5:35 am Post subject: solved |
|
|
Apprentice
Joined: 23 Jun 2004
Posts: 29
|
Thanks Peter - that was the problem.
My triggered exe wasn't finishing, so the trigger monitor was hanging. I fixed the trigger exe so that even if something goes wrong during the execution of the exe, it won't hang.
Thanks a lot!
Jared
PS It's difficult to prepend that START command to change how the trigger program is run at our company. I think that would involve modifying the trigger queue definition or the process definition to prepend that START command. Our company has outsourced maintenance of our servers and queue managers, so modifying queue definitions is quite slow. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 13, 2005 5:56 am Post subject: Re: solved |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| jared_hagel wrote: |
| It's difficult to prepend that START command to change how the trigger program is run at our company. I think that would involve modifying the trigger queue definition or the process definition to prepend that START command. Our company has outsourced maintenance of our servers and queue managers, so modifying queue definitions is quite slow. |
You should always invoke batch or script files from triggers, instead of directly invoking exes.
This would allow you to change the batch file to start your processing in another shell, rather than having to change the queue definition.
There are also a lot of other reasons for doing this. Like if the exe changes names or needs new parameters or etc...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
