| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue with SwA parsing |
« View previous topic :: View next topic » |
| Author |
Message
|
| abhishekpreddy |
 Posted: Fri Mar 26, 2010 10:13 am Post subject: Issue with SwA parsing |
 |
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
Hi,
We have a requirement to integrate with a Web service which responds back with SwA , we are using broker 6.0 so we cannot use the latest SOAP nodes , I have tried all options on the HttpRequest node , MIME , canned message sets provided by IBM for MIME with attachements type , but none seem to work , any help would be much appreciated |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Fri Mar 26, 2010 11:17 am Post subject: Re: Issue with SwA parsing |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| abhishekpreddy wrote: |
| but none seem to work |
I've seen problems such as this before. Its normally caused by an error somewhere. Exactly what yours could be its impossible to tell as you havent shared any details about what issues you have had or what you've tried.
Have you tried turning the computer off and on again?
Details about what didnt work, usertraces and /or trace node dumps may help people to understand your problem and offer better advice. You should be able to parse SwA however so your goal should be achievable.
Last edited by WMBDEV1 on Fri Mar 26, 2010 11:29 am; edited 1 time in total |
|
| Back to top |
|
|
| abhishekpreddy |
| Posted: Fri Mar 26, 2010 11:29 am Post subject: |
|
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
Hi ,
The service trace is too huge for me to attach it here , ok here is what I am trying to do MQInput --> Compute --> HttpRequest --> Compute --> MQOutput , on the HttpRequest node i am setting the response parser set to MIME , but when ther response comes back it complains that it cant parse the header at &1 not sure what that means , but if you have had any experience before with integrating with SwA web service could you let me know if we need to set anything specific in the headers before passing it to the HttpRequest node , it would be of great help |
|
| Back to top |
|
|
| abhishekpreddy |
| Posted: Fri Mar 26, 2010 11:39 am Post subject: |
|
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
| Empty of Invalid Header found at position &1 , this is the error message the HttpRequest node throws on receiving the response , when i test the Web service using SOAP UI and a Junit Java class it works perfect not sure what needs to be tweeked in HttpRequest node props. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Mar 26, 2010 12:58 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Please explain why you, as a user, are using service trace? Why not user trace, or the debugger, or Trace nodes, or the system log? |
|
| Back to top |
|
|
| abhishekpreddy |
| Posted: Fri Mar 26, 2010 1:29 pm Post subject: |
|
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
Hi Kimbert,
We are using service trace because from the user trace or the trace nodes or the debugger we could not get much help , on examining the user trace we found that the HttpRequest nodes reads the data from the socket correctly but it fails when it tried to create the logical MIME structure.
here is a part of the User trace if that would be useful
2010-03-26 14:25:27.641036 1596 UserTrace BIP2537I: Node 'TestHttp.Compute2': Executing statement ''SET OutputRoot.Properties.ReplyProtocol = 'SOAP-HTTP';'' at ('.TestHttp_Compute2.Main', '5.3').
2010-03-26 14:25:27.641235 1596 UserTrace BIP2566I: Node 'TestHttp.Compute2': Assigning value '''SOAP-HTTP''' to field / variable ''OutputRoot.Properties.ReplyProtocol''.
2010-03-26 14:25:27.641328 1596 UserTrace BIP2537I: Node 'TestHttp.Compute2': Executing statement ''SET OutputRoot.Properties.ContentType = 'text/xml; charset=UTF-8';'' at ('.TestHttp_Compute2.Main', '6.3').
2010-03-26 14:25:27.641492 1596 UserTrace BIP2566I: Node 'TestHttp.Compute2': Assigning value '''text/xml; charset=UTF-8''' to field / variable ''OutputRoot.Properties.ContentType''.
2010-03-26 14:25:27.641546 1596 UserTrace BIP2537I: Node 'TestHttp.Compute2': Executing statement ''SET OutputRoot.MQMD = NULL;'' at ('.TestHttp_Compute2.Main', '7.3').
2010-03-26 14:25:27.641651 1596 UserTrace BIP2567I: Node 'TestHttp.Compute2': Assigning NULL to ''OutputRoot.MQMD'', thus deleting it.
2010-03-26 14:25:27.641708 1596 UserTrace BIP2537I: Node 'TestHttp.Compute2': Executing statement ''SET OutputRoot.HTTPRequestHeader.Content-Type = 'text/xml; charset=UTF-8';'' at ('.TestHttp_Compute2.Main', '8.3').
2010-03-26 14:25:27.642166 1596 UserTrace BIP2566I: Node 'TestHttp.Compute2': Assigning value '''text/xml; charset=UTF-8''' to field / variable ''OutputRoot.HTTPRequestHeader.Content-Type''.
2010-03-26 14:25:27.642227 1596 UserTrace BIP2537I: Node 'TestHttp.Compute2': Executing statement ''SET OutputRoot.HTTPRequestHeader.SOAPAction = 'ComposeResponse';'' at ('.TestHttp_Compute2.Main', '9.3').
2010-03-26 14:25:27.642356 1596 UserTrace BIP2566I: Node 'TestHttp.Compute2': Assigning value '''ComposeResponse''' to field / variable ''OutputRoot.HTTPRequestHeader.SOAPAction''.
2010-03-26 14:25:27.642469 1596 UserTrace BIP2537I: Node 'TestHttp.Compute2': Executing statement ''SET OutputRoot.HTTPRequestHeader.Host = 'iwasint.standard.com';'' at ('.TestHttp_Compute2.Main', '10.3').
2010-03-26 14:25:27.642574 1596 UserTrace BIP2566I: Node 'TestHttp.Compute2': Assigning value '''iwasint.standard.com''' to field / variable ''OutputRoot.HTTPRequestHeader.Host''.
2010-03-26 14:25:27.642629 1596 UserTrace BIP2537I: Node 'TestHttp.Compute2': Executing statement ''SET OutputRoot.XMLNS = InputRoot.XMLNS;'' at ('.TestHttp_Compute2.Main', '11.3').
2010-03-26 14:25:27.642770 1596 UserTrace BIP2539I: Node 'TestHttp.Compute2': Evaluating expression ''InputRoot.XMLNS'' at ('.TestHttp_Compute2.Main', '11.26'). This resolved to ''InputRoot.XMLNS''. The result was ''ROW... Root Element Type=16777232 NameSpace='' Name='XMLNS' Value=''''.
2010-03-26 14:25:27.642829 1596 UserTrace BIP2568I: Node 'TestHttp.Compute2': Copying sub-tree from ''InputRoot.XMLNS'' to ''OutputRoot.XMLNS''.
2010-03-26 14:25:27.642957 1596 UserTrace BIP2537I: Node 'TestHttp.Compute2': Executing statement ''RETURN TRUE;'' at ('.TestHttp_Compute2.Main', '14.3').
2010-03-26 14:25:27.643110 1596 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'TestHttp.Compute2'.
2010-03-26 14:25:31.715536 1596 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'TestHttp.HTTP Request' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2010-03-26 14:25:31.718435 1596 UserTrace BIP6061I: Parser type ''HTTPResponseHeader'' created on behalf of node 'TestHttp.HTTP Request' to handle portion of incoming message of length '249' bytes beginning at offset '0'. Parser type selected based on value ''WSRSPHDR'' from previous parser.
2010-03-26 14:25:31.718992 1596 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'TestHttp.HTTP Request'.
2010-03-26 14:25:31.719453 1596 UserTrace BIP6061I: Parser type ''MIME'' created on behalf of node 'TestHttp.HTTP Request' to handle portion of incoming message of length '469345' bytes beginning at offset '249'. Parser type selected based on value ''MIME'' from previous parser.
2010-03-26 14:25:33.553909 1596 UserTrace BIP2537I: Node 'TestHttp.Compute1': Executing statement ''BEGIN ... END;'' at ('.TestHttp_Compute1.Main', '2.2').
2010-03-26 14:25:33.553989 1596 UserTrace BIP2537I: Node 'TestHttp.Compute1': Executing statement ''RETURN TRUE;'' at ('.TestHttp_Compute1.Main', '5.3').
2010-03-26 14:25:33.554092 1596 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'TestHttp.Compute1'.
2010-03-26 14:26:16.456394 2868 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2010-03-26 14:26:16.456542 2868 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Sat Mar 27, 2010 12:34 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| abhishekpreddy wrote: |
] on examining the user trace we found that the HttpRequest nodes reads the data from the socket correctly but it fails when it tried to create the logical MIME structure.
|
How did you confirm that?
From your trace it looks like the message has left the http request node and entered the second compute node (confusingly called compute1):
| Quote: |
| Code: |
2010-03-26 14:25:31.718992 1596 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'TestHttp.HTTP Request'.
2010-03-26 14:25:33.553909 1596 UserTrace BIP2537I: Node 'TestHttp.Compute1': Executing statement ''BEGIN ... END;'' at ('.TestHttp_Compute1.Main', '2.2').
2010-03-26 14:25:33.553989 1596 UserTrace BIP2537I: Node 'TestHttp.Compute1': Executing statement ''RETURN TRUE;'' at ('.TestHttp_Compute1.Main', '5.3').
|
|
What does the message tree look like between the http request and compute1 nodes?
If the compute1 node then passes the message to the MQOutput node i'd imagine it would fail as you have not formed a valid MQ message (at least not from the trace shown above). |
|
| Back to top |
|
|
| sguerin |
| Posted: Tue Sep 14, 2010 10:37 am Post subject: |
|
|
Newbie
Joined: 14 Sep 2010
Posts: 5
|
Hi abhishekpreddy,
Did you solve this issue, because I get a similar error when receiving a SwA reponse from a service web. |
|
| 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
|
|
|
|
