|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQCONNX not working with remote client |
« View previous topic :: View next topic » |
Author |
Message
|
cmkeller |
Posted: Wed Apr 18, 2007 6:48 am Post subject: MQCONNX not working with remote client |
|
|
Apprentice
Joined: 09 Jan 2005 Posts: 41 Location: Queens, NY
|
Using MQSeries 5.3 on Windows machines:
I have an application that uses a client connection to access MQSeries. There are two different parts to this application. One part uses the C++ interface, and connects by setting channel name, connection name, transport type and heartbeat interval in an ImqChannel object, then uses setConnectionReference to attach the ImqChannel to ImqQueueManager, and then ImqQueueManager connects just fine. That part works great, whether the server is remote or whether it is the same box as the client.
The other part uses MQCONNX. It initializes an MQCD structure with the "client connection channel" defaults, then sets channel name, connection name and short connection name. It then calls MQCONNX with this structure as a parameter. If the client and server are on the same box, everything is fine. But if the client is on a different box than the server, the connection fails with code 2058 - bad queue manager name.
The thing that puzzles me most is that I examined the contents of the underlying MQCD structure in the ImqChannel of the one that works right, it is identical to the contents of the one that doesn't work! And this is the same remote queue manager I'm trying to access from the same client machine, so it can't be a problem with the connection itself.
Anyone have any ideas? _________________ Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
Back to top |
|
 |
cmkeller |
Posted: Wed Apr 18, 2007 6:57 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2005 Posts: 41 Location: Queens, NY
|
Clarification:
I initialized my Connect Options structure to MQCNO_DEFAULT, then set the version to 2, and the channel pointer to my MQCD structure. I am calling MQCONNX with the MQCNO structure, thusly populated, as the parameter, not, as implied earlier, that I directly use the MQCD as a parameter for MQCONNX. _________________ Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Apr 18, 2007 7:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Do you link against mqic lib or mqm lib? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
cmkeller |
Posted: Wed Apr 18, 2007 8:33 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2005 Posts: 41 Location: Queens, NY
|
Hmm...the good one links to mqic, and the bad one to mqm.
THANK YOU! I changed it and it works. This had been driving me nuts for a week!
I guess I'm too much of a coder to have thought about the library linkings. Wow, you got that fast. _________________ Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Apr 18, 2007 9:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
A 2058 from a client when the qmgr name is known to be correct is almost always a failure to link against the client library. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|