| Author |
Message
|
| javaforvivek |
 Posted: Tue Oct 22, 2002 10:19 pm Post subject: Unable to start Trigger Monitor |
 |
|
Master
Joined: 14 Jun 2002
Posts: 282
Location: Pune,India
|
Hello,
I've installed IBM-MQSeries version 5.2 on Win2K Advanced Server with SP2.
When i try to start the Trigger Monitor for certain Queue Manager,viz, VIVQMGR, Using following command :
| Code: |
| [i]runmqtrm -m VIVQMGR -q DEFAULT.INITQ[/i] |
Where DEFAULT.INITQ is the default initiation queue for VIVQMGR.
it gives the error message as follows:
Queue Manager not available to the MQSeries Trigger Monitor.
MQSeries Trigger Monitor ended.
I'm logging in as administrator to the machine and 've included administrator in the mqm user group.
I'm trying to start the Trigger Monitor throught a terminal client connection to the Win2K server where the MQServer is installed.
Rest of the things like connecting to the QueueManager via a MQ For java client, putting messges on the Queues and getting them back do work fine even from remote locations.
Can anybody give the reason why it's happening???
Regards,
Vivek |
|
| Back to top |
|
 |
| udaybho |
| Posted: Wed Oct 23, 2002 4:48 am Post subject: |
|
|
Voyager
Joined: 09 May 2002
Posts: 94
Location: Chicago
|
Try the same command from Win2K server console.
Uday Bhosle |
|
| Back to top |
|
|
| leongor |
| Posted: Wed Oct 23, 2002 9:30 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
The problem is terminal client.
When using it, you cannot work with binding mode connecting to Qmgr.
But client works fine (through TCP/IP).
If you want still connect via binding - you can do it with telnet.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| 2189 |
| Posted: Thu Oct 24, 2002 7:02 am Post subject: |
|
|
Apprentice
Joined: 22 Oct 2002
Posts: 31
|
I think this is reiterating what Leongor has said but..
By terminal client do you mean Terminal Services cos MQ ain't supported using Terminal Services? MQ Explorer and dspmq will say the qmgr ain't running when it is.
Instead you have to connect using Telnet or a Remote command server session. Ironically, you can connect to a server using Terminal services and then telnet to another server and it will work.
_________________
2189 errors make me  |
|
| Back to top |
|
|
| javaforvivek |
| Posted: Mon Nov 11, 2002 8:30 pm Post subject: |
|
|
Master
Joined: 14 Jun 2002
Posts: 282
Location: Pune,India
|
Hello and Thanx to all of u for giving some imp.. suggestions.
But now, I am facing another problem for this Trigger Monitor on my own machine (it's a WinNT 4.0 SP 6 Server).
I have created the same VIVEKQMGR with the follwing queues:
Transmission Queue: DEFAULT.XMITQ
Dead Letter Queue: DEFAULT.DEADQ
Other queues : USER1Q,USER2Q,DEFAULT.INITQ
For USER2Q, I am keeping Triggering ON and specifying Initiation Queue as DEFAULT.INITQ.
Now, when I start the Trigger Monitor with command:
runmqtrm -m VIVEKQMGR -q DEFAULT.INITQ
It shows:
MQSeries Trigger Monitor started
Initiation Queue in use
MQSeries Trigger Monitor ended
But when I start the Trigger Monitor with some other Queue name
for eg:
runmqtrm -m VIVEKQMGR -q SYSTEM.DEFAULT.INITIATION.QUEUE
or
runmqtrm -m VIVEKQMGR -q USER1Q
The trigger Monitor starts successfully.
What may be the reason for trigger monitor not starting with DEFAULT.INITQ; where DEFAULT.INITQ IS untouched throught out the application????
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth. |
|
| Back to top |
|
|
| leongor |
| Posted: Tue Nov 12, 2002 8:15 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
First of all the my recommendation is to upgrade NT to SP6A.
Can it possible that you have defined trigger monitor as a MQ Service with this DEFAULT.INITQ ?
Then you cannot run another one with it again.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
|
|
