| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Debugging MQSOAP.DLL (MA0R) |
« View previous topic :: View next topic » |
| Author |
Message
|
| zberger@knology.net |
 Posted: Fri Apr 09, 2004 8:22 am Post subject: Debugging MQSOAP.DLL (MA0R) |
 |
|
Newbie
Joined: 09 Apr 2004
Posts: 2
|
I have been trying to use the MQ Transport for SOAP from IBM's MA0R SupportPac. Putting the soap requests works fine, and it is received back on the client just fine, but it fails to deserialize.
I turned on tracing and it shows the response stream is received -- but it throws an exception saying "The data at the root level is invalid. Line 1, position 1". The problem with that is, the message is a valid xml/soap response.
What I'm looking for is some way to get more information about this process. The MQSOAP.DLL does not have source available, so I can't just stop it in the debugger. The trace facility is nice, but doesn't just give much information. Is there any way to dump the actual message as received in the DLL? It looks fine on the receiving client queue manager.
I'm worried that the MQSOAP.DLL might be trying to do another char set conversion or something strange. Any thoughts or ideas would be very helpful.
TIA,
Joe Z. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sat Apr 10, 2004 8:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'd suspect that either you have an extra line ending at the front of your message, or your Soap message is in Windows ASCII or something when the support pack is expecting Unicode.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| zberger@knology.net |
| Posted: Sun Apr 11, 2004 8:12 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2004
Posts: 2
|
That is what I am suspecting. I have, however, tried two things.
The first is to change my services endpoint from a "wmq" url to an "http" url. when I do this, the message deserializes quite nicely using the standard .NET WebRequest/WebResponse classes for http.
The second was to grab a copy of the message on the client connection queue manager. It looked fine, but I'm not sure it that guarentees that it will not attempt to convert it to another charset on the last hop to the client machine and the MQSOAP dll.
Do you know of any way to trace what is going on in the MQSOAP dll (beyond the tracing property, which, while useful, doesn't provide any information about the data).
If I could just see what it is getting, I'm sure I could figure it out. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Apr 11, 2004 8:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| zberger@knology.net wrote: |
| The second was to grab a copy of the message on the client connection queue manager. It looked fine, but I'm not sure it that guarentees that it will not attempt to convert it to another charset on the last hop to the client machine and the MQSOAP dll. |
What did you use to look at it, that you're sure it looks fine? What was the CCSID of the message?
Which tracing property are you talking about? One on the DLL? Did you try enabling MQSeries tracing on the "client connection queue manager"?
The only other thing I can think of is to write an API exit or a channel exit to watch the client connection.
Or, if the support pack is a supported support pack, you could open a ticket with IBM.
_________________
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
|
|
|
|
