| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Client upgrade ver. 6 => 7, Exceptions |
« View previous topic :: View next topic » |
| Author |
Message
|
| 4integration |
 Posted: Mon Jan 04, 2010 12:47 am Post subject: Client upgrade ver. 6 => 7, Exceptions |
 |
|
Disciple
Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
|
Hi,
I have executed version 6 of WMQ Client together with IBM.XMS 1.2.7.0 for a long time.
Now I upgraded WMQ Client to version 7 in order to begin development with version 7 instead (also requiring upgrade to IBM.XMS v2.0). But I get strange exceptions when connecting:
| Quote: |
CWSMQ0006E: An exception was received during the call to the method ConnectionFactory.CreateConnection: CompCode: 2, Reason: 2058. During execution of the specified method an exception was thrown by another compo
nent. See the linked exception for more information. LinkedException: MQRC_Q_MGR_NAME_ERROR
at GimXmsApi.Base.GimBaseWmq..ctor(IGimWmqConnectionInfo ConnectionInfo, Boolean Transacted)
at GimXmsApi.GimWmqReader..ctor(IGimWmqConnectionInfo ConnectionInfo, Boolean Transacted)
at GimXmsApp.Program.SelectorTest(String FileToSend)
at IBM.XMS.Client.WMQ.WmqConnectionFactory.CreateProviderConnection(XmsPropertyContext connectionProps)
at IBM.XMS.Client.Impl.XmsConnectionFactoryImpl.CreateConnection(String userID, String password)
at IBM.XMS.Client.Impl.XmsConnectionFactoryImpl.CreateConnection()
at GimXmsApi.Base.GimBaseWmq.CreateConnection(IConnectionFactory cf)
at GimXmsApi.Base.GimBaseWmq.StartConnection()
at GimXmsApi.Base.GimBaseWmq..ctor(IGimWmqConnectionInfo ConnectionInfo, Boolean Transacted) |
Previously I have done som pre-testing with WMQ 7 and that worked...and I can not remember any required client implementation change...
Any idea would be helpful!!!
EDIT: Worth to mention is that MQMON and RFHUtil is working from the client machine
_________________
Best regards
4 Integration |
|
| Back to top |
|
 |
| 4integration |
| Posted: Mon Jan 04, 2010 1:56 am Post subject: |
|
|
Disciple
Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
|
The previous test was done with ConnectionMode XMSC.WMQ_CM_CLIENT_UNMANAGED and if I switch to XMSC.WMQ_CM_CLIENT I instead get:
PS. The queue manager is running on 6.0.2.7. DS.
| Code: |
[10:53:16.968] ===============================================================================
[10:53:16.984] Cleaning
[10:53:17.000] ===============================================================================
[10:53:17.156] Connection with the following info
[10:53:17.171] Hostname...........: 192.168.197.128
[10:53:17.171] QueueManagerName...: WBRK61_DEFAULT_QUEUE_MANAGER
[10:53:17.187] PortNumber.........: 2414
[10:53:17.203] ConnectionMode.....: 1
[10:53:17.203] ChannelName........: DOTNET.CHANNEL
[10:53:17.250] WMQ Client version.: 7
[10:53:17.484] GimBaseWmq::CloseConnection
[10:53:17.500] GimBaseWmq::Dispose
EXCEPTION in SelectorTest
CWSMQ0006E: An exception was received during the call to the method ConnectionFactory.CreateConnection: IBM.WMQ.Nmqi.NmqiException: Exception of type 'IBM.WMQ.Nmqi.NmqiException' was thrown.
at IBM.WMQ.Nmqi.ManagedNmqiMQ.NmqiConnect(String name, NmqiConnectOptions pNmqiConnectOpts, MQConnectOptions cno, Hconn parentHconn, Phconn pHconn, Int32& compCode, Int32& reason)
at IBM.XMS.Client.WMQ.WmqConnection..ctor(NmqiEnvironment nmqiEnv, NmqiMQ nmqiMQ, XmsPropertyContext connectProps)
at IBM.XMS.Client.WMQ.WmqConnectionFactory.CreateV7ProviderConnection(XmsPropertyContext connectionProps). During execution of the specified method an exception was thrown by another component. See the linked
exception for more information. LinkedException: MQRC_CLIENT_CONN_ERROR
at GimXmsApi.Base.GimBaseWmq..ctor(IGimWmqConnectionInfo ConnectionInfo, Boolean Transacted)
at GimXmsApi.GimWmqReader..ctor(IGimWmqConnectionInfo ConnectionInfo, Boolean Transacted)
at GimXmsApp.Program.SelectorTest(String FileToSend)
at IBM.XMS.Client.WMQ.WmqConnectionFactory.CreateProviderConnection(XmsPropertyContext connectionProps)
at IBM.XMS.Client.Impl.XmsConnectionFactoryImpl.CreateConnection(String userID, String password)
at IBM.XMS.Client.Impl.XmsConnectionFactoryImpl.CreateConnection()
at GimXmsApi.Base.GimBaseWmq.CreateConnection(IConnectionFactory cf)
at GimXmsApi.Base.GimBaseWmq.StartConnection()
at GimXmsApi.Base.GimBaseWmq..ctor(IGimWmqConnectionInfo ConnectionInfo, Boolean Transacted)
[10:53:17.656] Done - Exit |
_________________
Best regards
4 Integration |
|
| Back to top |
|
|
| 4integration |
| Posted: Mon Jan 04, 2010 2:09 pm Post subject: |
|
|
Disciple
Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
|
I tested my client towards another queue manager (v6) and that worked. Switching back to my test QM and the errors came back.
Also tested a simple native WMQ client application (not via XMS) and that works.
When I used the v6 client and switched to v7, is something cached or similar that needs to be cleared/reset??!
_________________
Best regards
4 Integration |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jan 04, 2010 3:48 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| LinkedException: MQRC_CLIENT_CONN_ERROR |
Did you search Mr. Google for MQRC_CLIENT_CONN_ERROR? The very first hit gave me the official doc from IBM.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| 4integration |
| Posted: Tue Jan 05, 2010 11:15 am Post subject: |
|
|
Disciple
Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
|
Ok, so the search gave "...the official doc from IBM..." telling "...but the MQCD channel definition structure is not specified correctly..."
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.amqzao.doc/fm14400_.htm
and IBM states in XMS doc:
"Any application that uses an older version of XMS .NET (say, V1.2.7 or V1.2.6) can install a newer version of XMS (V2.0 or above) and subsequently run on the newer XMS version without a need for recompilation."
So, bruce2359, if you got useful information from Mr Google, please post the URL, that would be more helpful instead of being sarcastic.
Since the client works to some queue managers but not recently tested, WMQ API works as well as other tooling (not using XMS) I suspect some issue with XMS or/and in combination with operating system APIs (MS Windows)
EDIT: Have also registered a PMR
_________________
Best regards
4 Integration |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 05, 2010 11:36 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I had not intended any sarcasm in my response. I had intended to point to the useful information embedded in the output you posted, and to suggest that you continue your search.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| dutilleul |
| Posted: Tue Jan 26, 2010 6:53 am Post subject: |
|
|
Newbie
Joined: 23 Feb 2006
Posts: 7
Location: Bruxelles
|
Hi
We have the same problem with a very basic .Net XMS application who only connect to the qmgr and disconnect immediately.
Our investigations still continue, but I just wonder what is the current status of your problem, and what did IBM respond ?
It seems that the problem cames with the fact that the XMS application is running on an MQClient v7 and try to connect to a qmgr still in v6.
After analysing traces, we have found that in the Connection Factory, there is a properties called ProviderVersion who allow you to run in normal mode or in "migration" mode. You can force here the command level of the target qmgr.
The default value is "unspecified" which mean that the connection Factory will first connect to the qmgr to inquire the command level, then it disconnect and assign the ProviderVersion properties to the good value.
We've just see in the traces that even if the target qmgr is in version 6.0.x, the ProviderVersion is assigned with value 7 and so the connect doesn't works:
First Connect :
| Code: |
17:28:27.913591 5736.0001 IBM.XMS.Client.WMQ.WmqConnectionFactory --- > WMQConnectionModePropertyValidator.Validate(Object,Object) entry [o] 1
XMSC_WMQ_PROVIDER_VERSION : unspecified
17:28:28.085469 5736.0001 IBM.XMS.Client.Impl.XmsReadablePropertyC - d GetObjectProperty(String) [o] XMSC_WMQ_PROVIDER_VERSION, [o] unspecified
|
| Code: |
| 17:28:28.397975 5736.0001 IBM.XMS.Client.WMQ.WmqConnectionFactory > CreateV7ProviderConnection(XmsPropertyContext) entry |
| Code: |
17:28:30.991775 5736.0001 IBM.XMS.Client.WMQ.WmqConnectionFactory > CheckConnectionV7Capable(WmqConnection,String,bool) entry
17:28:30.991775 5736.0001 IBM.XMS.Client.WMQ.WmqConnection > CMDLevel.get() entry
17:28:30.991775 5736.0001 IBM.XMS.Client.WMQ.WmqConnection < CMDLevel.get() exit
17:28:30.991775 5736.0001 IBM.XMS.Client.WMQ.WmqConnection > SharingConversations.get() entry
17:28:30.991775 5736.0001 IBM.XMS.Client.WMQ.WmqConnection < SharingConversations.get() exit
17:28:30.991775 5736.0001 IBM.XMS.Client.WMQ.WmqConnectionFactory d CMD Level = 600
17:28:30.991775 5736.0001 IBM.XMS.Client.WMQ.WmqConnectionFactory d SharingConversations = 10
17:28:30.991775 5736.0001 IBM.XMS.Client.WMQ.WmqConnectionFactory d CheckConnectionV7Capable(WmqConnection,String,bool) , [color=red][b]CmdLevel < 700; not a v7 capable QM[/b][/color]
17:28:30.991775 5736.0001 IBM.XMS.Client.WMQ.WmqConnectionFactory < CheckConnectionV7Capable(WmqConnection,String,bool) exit
17:28:30.991775 5736.0001 NLSHelper e Could not produce a message with the key CreateProviderConnection(XmsPropertyContext) |
The first connect : XMSC_WMQ_PROVIDER_VERSION : unspecified
The second connect : XMSC_WMQ_PROVIDER_VERSION : 7
It look to us like an issue but we don't have any competence in the world of JMS, XMS or .NET. so it's difficult for us to be sure that this is the root cause of the problem.
We are going to open a PMR but I just wonder if that it was not yet fixed in 7.0.1.1. and if you already resolved it.
Thanks for any answer...even sarcastics one.  |
|
| Back to top |
|
|
| 4integration |
| Posted: Tue Jan 26, 2010 7:07 am Post subject: |
|
|
Disciple
Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
|
Hello,
I got a fix for XMS.NET v2.0 called "ia9h_v2.0_IZ63166" that solved the connection issue.
_________________
Best regards
4 Integration |
|
| Back to top |
|
|
| dutilleul |
| Posted: Wed Jan 27, 2010 12:12 am Post subject: |
|
|
Newbie
Joined: 23 Feb 2006
Posts: 7
Location: Bruxelles
|
| Quote: |
Hello,
I got a fix for XMS.NET v2.0 called "ia9h_v2.0_IZ63166" that solved the connection issue. |
Hello,
Thank you very much for your quick answer.
I still have a question.
Is this a fix build by IBM about an MQ component or is this a fix provided by Microsoft about the .NET framework ?
The terminology of the fixname looks like IBM, but you said that it's a fix for XMS.NET v2.0, so I'm a little bit confuse.
Due to my different investigations, I expect a modification of an MQ JMS class, but I'm not sure.
I just want to be certain that I ask the right thing to the right supplier.
Once again, thank you for your help. |
|
| Back to top |
|
|
| 4integration |
| Posted: Wed Jan 27, 2010 12:32 am Post subject: |
|
|
Disciple
Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
|
In my case it was a fix of IBM Message Service Client for .NET a.k.a XMS.NET.
There was no bug in WMQ Client nor MS Windows.
_________________
Best regards
4 Integration |
|
| Back to top |
|
|
| dutilleul |
| Posted: Wed Jan 27, 2010 3:10 am Post subject: |
|
|
Newbie
Joined: 23 Feb 2006
Posts: 7
Location: Bruxelles
|
|
| 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
|
|
|
|
