| Author |
Message
|
| hsa |
 Posted: Wed Feb 17, 2010 6:37 am Post subject: get error: URI address for connecting MQ/zOS from .net(WCF) |
 |
|
Newbie
Joined: 17 Feb 2010
Posts: 5
|
hi
env: MQClient=v7.0.1, .net=v3.5
Please help,
I cannot figure it out what is the correct format for running the example: <MQClient_home>\Tools\wcf\samples\WCF\oneway
I get exception for this config:
| Code: |
<client>
<endpoint address="jms:/queue?destination=JB.WEBS.DOTNET.REQUEST@MQU1&connectionFactory=connectQueueManager(MQU1)clientConnection(MVSPF(1415))clientChannel(CLIENT.TO.MQU1)&initialContextFactory=com.ibm.mq.jms.Nojndi"
binding="customBinding" bindingConfiguration="CustomBinding_IWMQSampleContract"
contract="IWMQSampleContract" name="CustomBinding_IWMQSampleContract" />
</client>
|
error System.ServiceModel.CommunicationException: WCFCH0307E: An error occurred while
attempting to send data for endpoint 'jms:/queue?destination=JB.WEBS.DOTNET.REQU
EST@MQU1&connectionFactory=connectQueueManager(MQU1)clientConnection(MVSPF(1415)
)clientChannel(CLIENT.TO.MQU1)&initialContextFactory=com.ibm.mq.jms.Nojndi' The
operation could not be completed. Review the linked exception for further detail
s. ---> IBM.XMS.InvalidDestinationException: The specified value 'IBM.XMS.Client
.WMQ' is not allowed for 'Expected ConnectionType = '. The given value is not al
lowed for the property specified. Change the value to a value that is supported
for the property.
at IBM.XMS.Client.Impl.XmsMessageImpl.set_JMSReplyTo(IDestination value)
at IBM.XMS.WCF.XmsChannelHelper.WriteSoapJMSRequestMessageContents(IBytesMess
age msg, ArraySegment`1 msgBody, IDestination jmsRepyTo, String endpointURL, Str
ing targetService, String soapAction, Byte[] correlId, Boolean oneWay)
at IBM.XMS.WCF.XmsOutputChannel.<BeginSend>b__1(AsyncTimedResult ar, Object p
aram)
--- End of inner exception stack trace --- |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Feb 17, 2010 7:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Moved to more relevant section
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 17, 2010 7:57 am Post subject: Re: get error: URI address for connecting MQ/zOS from .net(W |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hsa wrote: |
| I cannot figure it out what is the correct format for running the example |
If you didwhat it said, specifically:
| hsa wrote: |
| Review the linked exception for further details. |
you'd gain an insight into what was wrong with your setup
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| hsa |
| Posted: Thu Feb 18, 2010 5:16 am Post subject: Re: get error: URI address for connecting MQ/zOS from .net(W |
|
|
Newbie
Joined: 17 Feb 2010
Posts: 5
|
| Vitor wrote: |
| hsa wrote: |
| Review the linked exception for further details. |
you'd gain an insight into what was wrong with your setup |
"error says":
| Code: |
The specified value 'IBM.XMS.Client.WMQ' is not allowed for 'Expected ConnectionType = '. The given value is not allowed for the property specified. Change the value to a value that is supported for the property.
|
What is the correct property?
FYI: I can run the following with NO problems:
| Code: |
using amqmdnet.dll::
<MQClient_home>\Tools\dotnet\samples\cs>nmqsput.exe JB.WEBS.DOTNET.REQUEST MQU1 CLIENT.TO.MQU1/TCP/MVSPF(1415) |
| Code: |
using IBM.XMS::
<MQClient_home>\Tools\dotnet\samples\bin\SampleConsumerCS.exe
AND
<MQClient_home>\Tools\dotnet\samples\bin\SampleProducerCS.exe |
|
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 18, 2010 6:23 am Post subject: Re: get error: URI address for connecting MQ/zOS from .net(W |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hsa wrote: |
"error says":
| Code: |
The specified value 'IBM.XMS.Client.WMQ' is not allowed for 'Expected ConnectionType = '. The given value is not allowed for the property specified. Change the value to a value that is supported for the property.
|
|
That's the error from .NET, not the linked error from the underlying provider (in this case WMQ). That's why the text is telling you to look elsewhere; that message was not included just to make the message longer!
| hsa wrote: |
FYI: I can run the following with NO problems:
| Code: |
using amqmdnet.dll::
<MQClient_home>\Tools\dotnet\samples\cs>nmqsput.exe JB.WEBS.DOTNET.REQUEST MQU1 CLIENT.TO.MQU1/TCP/MVSPF(1415) |
| Code: |
using IBM.XMS::
<MQClient_home>\Tools\dotnet\samples\bin\SampleConsumerCS.exe
AND
<MQClient_home>\Tools\dotnet\samples\bin\SampleProducerCS.exe |
|
None of this surprises me and confirms that you need to look in the linked exception. As well as reviewing the Client & Using .NET WMQ documentation. Specifically the parts about connection methods.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 18, 2010 9:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And making sure that you are not using features of the client that aren't supported by your server (2 versions back (5.3)?  )
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| hsa |
| Posted: Mon Feb 22, 2010 2:48 am Post subject: |
|
|
Newbie
Joined: 17 Feb 2010
Posts: 5
|
Thanks to Philippe D. fra IBM that investigate the problem.
.
"I was able to run the oneway sample connection either to a local Windows qmgr (client mode) or a remote AIX qmgr.
Both qmgrs were running V7.0.1. Then I tried to do the same on Z/os qmgrs and was able to connect to my V7.0 Z/os qmgr but got the same error as you when trying to connect to a Z/os V6 qmgr"
.
"I looked in the MQ documentation and found that WCF is only able to talk to V7 qmgrs not V6." |
|
| Back to top |
|
|
| gerbenvl |
| Posted: Tue Jul 13, 2010 1:03 am Post subject: |
|
|
Newbie
Joined: 13 Jul 2010
Posts: 2
|
| Also hit this error with WMQ7. In my case it popped up when the "Sharing Conversations" on the channel was set to "0". Setting it higher resolved the issue. |
|
| Back to top |
|
|
|
|
