| Author |
Message
|
| sstubble |
 Posted: Fri Dec 09, 2005 3:54 pm Post subject: WMQTool and AMQ9519 error |
 |
|
Novice
Joined: 09 Dec 2005
Posts: 20
|
| I have this tool installed on several servers. It works great except that on all but one of the servers I get an AMQ9519 error generated every time someone clicks on the icon to start the tool. Remote or local login to the server doesn't matter. Most all are running Windows 2003 Server SP1 and Java 2 Runtime Environment (Standard Edition build 1.4.0). Any ideas? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Dec 09, 2005 4:20 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
AMQ9519 says that there is an insert that should list the name of the channel in question.
What channel name is listed in the error?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sstubble |
| Posted: Fri Dec 09, 2005 4:47 pm Post subject: |
|
|
Novice
Joined: 09 Dec 2005
Posts: 20
|
| The AMQ9519 shows the queue manager name. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Dec 09, 2005 5:23 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That might be the problem... Has this worked previously, and something changed?
Or is this a new setup?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sstubble |
| Posted: Sat Dec 10, 2005 10:13 am Post subject: |
|
|
Novice
Joined: 09 Dec 2005
Posts: 20
|
| I decided to go in and defined svrconn channels with the name of the host queue manager on each of the queue managers. This made the errors stop generating. I'd still like to know though why one server did not exhibit the problem, even though it does not have the svrconn channels with the queue manager name defined. The only difference I can find is that it is not under windows domain control. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Dec 10, 2005 12:44 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So you identified that the problem was that you were trying to use a Queue manager name as a channel name.
It's possible that the one that did work has the Queue Manager as the default qmgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sstubble |
| Posted: Sun Dec 11, 2005 5:35 pm Post subject: |
|
|
Novice
Joined: 09 Dec 2005
Posts: 20
|
| The WMQTool must try to use the queue manager name as a channel name although it continues to work even if a channel with the same name as the queue manager isn't defined. I don't know if the one queue manager is defined as the default queue manager but I doubt it. There are 3 queue managers on that server. Even if we had accidentaly defined one of them as default we should be getting the AMQ9519 on the other queue mangers on that server. I've gone through the WMQTool documentation and haven't seen anything that tells me I need a svrconn channed with the queue manager named defined. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 12, 2005 4:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
According to http://www.niratul.com/QueueManager.htm,
| Quote: |
| Channel: You can enter the server connection channel name you want WMQTool to connect to. But it is optional. If you do not enter channel name here, WMQTool will first try to connect thru the server connection channel that of queue manager name and if it fails, it tries to connect thru SYSTEM.ADMIN.SVRCONN channel. In earlier versions, WMQTool also tried to connect thru SYSTEM.DEF.SVRCONN channel. But from version 4.0, this channel is no longer used for that purpose. This channel is used to connect any queue manager ONLY when you run 'Retrieve Queue Managers from the network' option on 'Select Queue Manager Tree' option while creating a shared file. |
My emphasis.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
