| Author |
Message
|
| sg_ric |
 Posted: Tue Oct 20, 2009 5:21 pm Post subject: MQ Upgrade Problem faced |
 |
|
Novice
Joined: 04 Jan 2009
Posts: 13
|
Hi,
Posting this forum to gain insight on where could be the problem, supplying "xxx" userid credential same as MCA userid on SERVER.DEF.SVRCONN is able to create connection and thus able to connect (able to pub/sub), however, in a mockup deployment whereby actual userid are being used, all of them threw an exception CWSMQ00006E upon creating connection, reason code 2058 (if i remembered correctly the error code, hehehe).
Therefore i tried setting the MCA userid to an actual userid (of mqm group), it actually works. Somehow only 1 userid can be connected?
I believed the problem could be on the authentication or settings at the MQ server.
Background:
I've upgraded my MQ server from V6.0.0.0 to V6.0.2.7.
Client machines connecting to the server had an update too. MQ client V7.0.1 with XMS v2 release Sep 09. WMQ connection between server and client. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Oct 20, 2009 5:33 pm Post subject: Re: MQ Upgrade Problem faced |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sg_ric wrote: |
| all of them threw an exception CWSMQ00006E upon creating connection, reason code 2058 (if i remembered correctly the error code, hehehe). |
Double check. I'd be surprised if a 2058 was an authentication issue.
[/quote]
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sg_ric |
| Posted: Tue Oct 20, 2009 6:34 pm Post subject: |
|
|
Novice
Joined: 04 Jan 2009
Posts: 13
|
The exception is as follow (from client)
CWSMQ0006E: An exception was received during the call to the mehtod ConnectionFactory.CreateConnection:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> IBM.XMS.XMSException: CWSMQ0006E: An exception was received during the call to the method WmqConnection.CreateQueueManager: CompCode: 2, Reason: 2058. During execution of the sepcified mehtod an exception was thrown by another component....
at IBM.XMS.WMQ.XmsWmqV6ConnectionWrapper.GetV6Connection(String username, String password, XmsPropertyContext connectionProperties) ........
At Server.
TCP/IP communication failure. 10054 (X'2746)
Think 2058 is unable to connect to the QMgr, or QMgr not found. In this case, i believe is the channel (SYSTEM.DEF.SVRCONN) not able to authenticate or so that why it threw 2058? |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Oct 20, 2009 11:12 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| sg_ric wrote: |
The exception is as follow (from client)
CWSMQ0006E: An exception was received during the call to the mehtod ConnectionFactory.CreateConnection:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> IBM.XMS.XMSException: CWSMQ0006E: An exception was received during the call to the method WmqConnection.CreateQueueManager: CompCode: 2, Reason: 2058. During execution of the sepcified mehtod an exception was thrown by another component....
at IBM.XMS.WMQ.XmsWmqV6ConnectionWrapper.GetV6Connection(String username, String password, XmsPropertyContext connectionProperties) ........
At Server.
TCP/IP communication failure. 10054 (X'2746)
Think 2058 is unable to connect to the QMgr, or QMgr not found. In this case, i believe is the channel (SYSTEM.DEF.SVRCONN) not able to authenticate or so that why it threw 2058? |
Fish time: MQRC_Q_MGR_NAME_ERROR and TCPIP Resets (RST) 461 10054
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Wed Oct 21, 2009 12:01 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
It looks like you're using the .Net client. I think if you explicity set the userid in .Net (as it seems you are) you get the 2058 errors, this is just the way the .Net client works.
Happy to be corrected though. |
|
| Back to top |
|
|
| sg_ric |
| Posted: Wed Oct 21, 2009 12:26 am Post subject: |
|
|
Novice
Joined: 04 Jan 2009
Posts: 13
|
| WMBDEV1 wrote: |
It looks like you're using the .Net client. I think if you explicity set the userid in .Net (as it seems you are) you get the 2058 errors, this is just the way the .Net client works.
Happy to be corrected though. |
Yes I did try both setting the userid and without setting the userid. Problem still surface.
However, if i set the userid to be the same as in the SERVER.DEF.SVRCONN MCA userid, it does not have any problem. It worked. Wonder is it possible for MCA userid, can i set MQM grp name instead of userid.
Hm... wat could be the problem.... hahaha |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 21, 2009 2:03 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sg_ric wrote: |
| WMBDEV1 wrote: |
It looks like you're using the .Net client. I think if you explicity set the userid in .Net (as it seems you are) you get the 2058 errors, this is just the way the .Net client works.
Happy to be corrected though. |
Yes I did try both setting the userid and without setting the userid. Problem still surface.
However, if i set the userid to be the same as in the SERVER.DEF.SVRCONN MCA userid, it does not have any problem. It worked. Wonder is it possible for MCA userid, can i set MQM grp name instead of userid.
Hm... wat could be the problem.... hahaha |
Could the problem be that you are not connecting where you think you are?
And thus the qmgr name is not right and authentication of anything different from mqm will throw you a bad return code...?
Make sure of where you are connecting to (channel, host, port) and verify that the qmgr name matches. And remember everything but the host name is case sensitive.
Oh BTW in a client connection a qmgr is uniquely identified by
- hostname
- port
- channel name
So you cannot access a qmgr on a port already in use by another qmgr or process.
And make sure your V7 client is in V6 compatibility mode.
I have never tried V7 client with XMS (which version of XMS)? to a V6 server. I sure hope they do not coexist on the same box.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Oct 21, 2009 2:44 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
...Could the problem be that you are not connecting where you think you are?
And thus the qmgr name is not right and authentication of anything different from mqm will throw you a bad return code...? |
And to reinforce that again - Fish time: MQRC_Q_MGR_NAME_ERROR and TCPIP Resets (RST) 461 10054
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| sg_ric |
| Posted: Wed Oct 21, 2009 7:58 am Post subject: |
|
|
Novice
Joined: 04 Jan 2009
Posts: 13
|
If the queue mgr connection setup is not properly configured, there shouldnt be any successful connection when i supplied the same userid in client machine and server MQ MCA Server.def.svronn userid.
Not sure is it MQ V6.0.2.7 not able to do authentication through user name server? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 21, 2009 11:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sg_ric wrote: |
If the queue mgr connection setup is not properly configured, there shouldnt be any successful connection when i supplied the same userid in client machine and server MQ MCA Server.def.svronn userid.
Not sure is it MQ V6.0.2.7 not able to do authentication through user name server? |
Define what you mean with user name server...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Oct 21, 2009 11:39 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Once more, and with feeling...
MQRC 2058 = MQRC_Q_MGR_NAME_ERROR
You got: An exception was received during the call to the method WmqConnection.CreateQueueManager: CompCode: 2, Reason: 2058
Investigate and correct this first before looking at (maybe) authentication errors.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| 4integration |
| Posted: Tue Oct 27, 2009 7:04 am Post subject: |
|
|
Disciple
Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
|
Did you find a solution?
I have the same problem....
_________________
Best regards
4 Integration |
|
| Back to top |
|
|
|
|
