| Author |
Message
|
| rivast_2001 |
 Posted: Tue Jul 20, 2004 7:52 am Post subject: WebSphere MQSeries and MA7K WebSphere MQ for Windows 2000 |
 |
|
Novice
Joined: 14 Jul 2004
Posts: 15
Location: Mansfield, MA
|
I am having some trouble trying to startup a Client Trigger Monitor Service on a Windows server. I installed the Client Trigger Monitor Service to monitor a queue on an iSeries machine. The configuration I used for the setup program is the following,
-------------------------
Global:
ShortTmr=60
ShortRty=10
LongTmr=1200
LongRty=999999999
EventLevel=2
WaitInterval=60000
MQSeriesDLL=mqic32.dll
Thread:
TriggerQueueName=RENEWAL.INITIATION.LOCAL.QUEUE
TriggerQueueMgrName=PRRENEWQM
---------------------
I am able to connect to the queue using a .NET application but when I am trying to startup the WebSphere MQ Client Trigger service. I am getting the following error.
------------------
"MQCONN" returned 2058 for queue "RENEWAL.INITIATION.LOCAL.QUEUE" and qmgr "PRRENEWQM", retrying...
-----------------
I also modified the MQSERVER variable to have the following value,
MQSERVER=TO.PRRENEWQM/TCP/10.10.10.15(1416)
Is it related to security somehow? Please advice,
Thanks in advance. |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Tue Jul 20, 2004 8:30 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Basically it is saying that PRRENEWQM does NOT live at 10.10.10.15(1416) .
Things to verify: queue manager name, channel name, IP address and port number.
Also, did you make the MQSERVER environment variable change global or local?
The other things that bugs me is your error message. You don't get a 2058 opening a queue. It is from the connection to the queue manager.
i.e.
"MQCONN" returned 2058 for connection attempt to qmgr "PRRENEWQM", retrying..
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| JT |
| Posted: Tue Jul 20, 2004 8:53 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| On the PRRENEWQM/10.10.10.15 machine, is there a Listener on port 1416? |
|
| Back to top |
|
|
| rivast_2001 |
| Posted: Tue Jul 20, 2004 9:03 am Post subject: |
|
|
Novice
Joined: 14 Jul 2004
Posts: 15
Location: Mansfield, MA
|
| Actually in this case all these information was valid. I was suspecting that was a Security issue and changed the account on the service to a local account in the machine instead of Local System Account and it worked. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Jul 20, 2004 9:21 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
That does not sound right. Because if you were having security problems, you would get 2035 rather than 2058!! What else did you change? 
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| rivast_2001 |
| Posted: Tue Jul 20, 2004 9:28 am Post subject: |
|
|
Novice
Joined: 14 Jul 2004
Posts: 15
Location: Mansfield, MA
|
I'll be honest and say that it was the only setting I changed.
Now I am running into another issue, which is that if I am posting 100 messages to the queue and I have the trigger setup for *ALL messages, I am only seeing that the program in the Windows machines gets triggered 4 times. The rest of the messages go to the SYSTEM.DEAD.LETTER.QUEUE queue. Any setting I missed during the installation of the Client Trigger Monitor Service ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 20, 2004 9:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Change your process definition to include 'start ' before it launches your executable.
But be aware that Trigger Type = ALL is not recommended, as it's not guaranteed to give you an initiation for every message.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
