ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP Input parsing error

Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next
 SOAP Input parsing error « View previous topic :: View next topic » 
Author Message
hotrock026
PostPosted: Tue Aug 26, 2014 9:42 am    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

help desk ,

sorry if iam worng....

actual message i can provide later as i dont have exact log now...

actual it saying soap bitsream error.... at an particular field....
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Aug 26, 2014 9:47 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

hotrock026 wrote:
help desk ,

sorry if iam worng....


A help desk is what IBM provide (and is a perfectly valid location for you to seek help, especially if you're against the clock as they do have an SLA)

hotrock026 wrote:
actual message i can provide later as i dont have exact log now...

actual it saying soap bitsream error.... at an particular field....


It is I think probative to determine a) what the parser thinks is bad about the bitstream and b) where in the bitstream this problem occurs as there are a number of potential problems with very different solutions.

Consider (as a random example which may in no way relate to your situation) where a SOAP call has been made where the payload contains an Eastern European character not supported in the code page identified for the document. This would yield a siimilar error at a different location to a SOAP call with the payload sent in double byte Unicode.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
hotrock026
PostPosted: Tue Aug 26, 2014 10:10 am    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Hi Vitor,

Yes ,Exactly even iam facing the issue is bit near to the example ,

my soap input node wsdl was unable to form an wsdl structure which i provided on the Soap Input Node where

Eg;-
In the Wsdl i have given field name has
<Sample>broker</Sample>
Where iam getting has
<Sample>broker</Sample1>
At this particular point Soap node trows an error saying Soap parser error which was unable to form the Structure at this particular filed because the field name which i provided in the wsdl is different from the field in the incoming payload...
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Aug 26, 2014 11:13 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

hotrock026 wrote:
At this particular point Soap node trows an error saying Soap parser error which was unable to form the Structure at this particular filed because the field name which i provided in the wsdl is different from the field in the incoming payload...


Never mind invalid because it doesn't match the WSDL, it's badly formed; the opening tag (Sample) doesn't match the end tag (Sample1).

So the SOAP Input node throws this error because the XML won't parse. You feed this to an RCD to turn it into a BLOB. What error does that throw that caused you to post here & ask for help?

Have you completely abandoned my suggestion?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
JosephGramig
PostPosted: Tue Aug 26, 2014 11:39 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA

hotrock026,

You are committing a great number of Word Crimes.
Back to top
View user's profile Send private message AIM Address
hotrock026
PostPosted: Tue Aug 26, 2014 11:48 am    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Hi Vitor,

The RCD also gives the same error.....like Soap node...
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
hotrock026
PostPosted: Tue Aug 26, 2014 11:50 am    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Hi JosephGramig,

Thxs for that i will not repeat and i will improve better..

iam here to solve my issue ,never mind for the words...but still thxs for that i will improve...
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Aug 26, 2014 12:32 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

hotrock026 wrote:
The RCD also gives the same error.....like Soap node...


Now why (I ask myself rhetorically) would the RCD be trying to parse the message body?

Perhaps it's time to give my idea more consideration. Or raise a PMR. Or wonder why that's happening.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
hotrock026
PostPosted: Tue Aug 26, 2014 1:12 pm    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Hi Vitor,

Thanks for that but still even i have an doubt ,y this RCD node allow one tiime parse to blob and the other time it will throw an error...

This is an consistency issue..

i will come back to you once the issue is fixed, thanks for your suggestions...

But finally ended with no solution
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
hotrock026
PostPosted: Tue Aug 26, 2014 1:23 pm    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

thanks all for your suggestions

pls update me if anyone as the solution...
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
hotrock026
PostPosted: Tue Aug 26, 2014 10:02 pm    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Hi,
[Exception]
[ATTRIBUTE Name = abcInqRq#FCMComposite_1_11]
[ATTRIBUTE Label = abcInqRq.Reset Content Descriptor]
[ATTRIBUTE Catalog = BIPmsgs]
[ATTRIBUTE Severity = 3]
[ATTRIBUTE Number = 2230]
[ATTRIBUTE Text = Node throwing exception]
[ELEMENT ParserException
[ATTRIBUTE File = /build/S700_P/src/WebServices/WSLibrary/ImbSOAPParser.cpp]
[ATTRIBUTE Line = 2150]
[ATTRIBUTE Function = ImbSOAPParser::createSoapShapedTree]
[ATTRIBUTE Type = ]
[ATTRIBUTE Name = ]
[ATTRIBUTE Label = ]
[ATTRIBUTE Catalog = BIPmsgs]
[ATTRIBUTE Severity = 3]
[ATTRIBUTE Number = 3614]
[ATTRIBUTE Text = problem creating SOAP tree from bitstream]
[ELEMENT ParserException
[ATTRIBUTE File = /build/S700_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCParser.cpp]
[ATTRIBUTE Line = 1101]
[ATTRIBUTE Function = ImbXMLNSCParser::parseRightSibling]
[ATTRIBUTE Type = ]
[ATTRIBUTE Name = ]
[ATTRIBUTE Label = ]
[ATTRIBUTE Catalog = BIPmsgs]
[ATTRIBUTE Severity = 3]
[ATTRIBUTE Number = 5009]
[ATTRIBUTE Text = XML Parsing Errors have occurred]
[ELEMENT ParserException
[ATTRIBUTE File = /build/S700_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCDocHandler.cpp]
[ATTRIBUTE Line = 634]
[ATTRIBUTE Function = ImbXMLNSCDocHandler::handleParseErrors]
[ATTRIBUTE Type = ComIbmSOAPInputNode]
[ATTRIBUTE Name = abcInqRq#FCMComposite_1_9]
[ATTRIBUTE Label = abcInqRq.SOAP Input]
[ATTRIBUTE Catalog = BIPmsgs]
[ATTRIBUTE Severity = 3]
[ATTRIBUTE Number = 5004]
[ATTRIBUTE Text = An XML parsing error has occurred while parsing the XML document]
[ELEMENT Insert
[ATTRIBUTE Type = 2]
[ATTRIBUTE Text = 1518]
]
[ELEMENT Insert
[ATTRIBUTE Type = 2]
[ATTRIBUTE Text = 2]
]
[ELEMENT Insert
[ATTRIBUTE Type = 2]
[ATTRIBUTE Text = 6]
]
[ELEMENT Insert
[ATTRIBUTE Type = 2]
[ATTRIBUTE Text = 48]
]
[ELEMENT Insert
[ATTRIBUTE Type = 5]
[ATTRIBUTE Text = The end-tag for element type "anb:Sample" must end with a ''>'' delimiter.]
]
[ELEMENT Insert
[ATTRIBUTE Type = 5]
[ATTRIBUTE Text = /XMLNSC/http://schemas.xmlsoap.org/soap/envelope/:Envelope/http://schemas.xmlsoap.org/soap/envelope/:Body/http://www.xyz.com/:abcInqRq/http://www.xyz.com/:MsgRqHdr/http://www.xyz.com/:Sample]
]
]
]
]
]
]
[/Exception]

this is the exception log thrown by the RCD Node.......
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
smdavies99
PostPosted: Tue Aug 26, 2014 10:33 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Are you really, really sure that the data is valid XML?

The error that you are seeing seems to indicate that?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
hotrock026
PostPosted: Tue Aug 26, 2014 10:44 pm    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

smdavies99,

Have you read all my post o just trying to post what you feel...


Even i know that the field name is worng now, iam here jus to handle those error scenarios to..when we are using the Soap nodes ,

Same question will asked by the Consumer , if have an dump of the input Payload i can answer them by showing the message...


That is the reason y iam trying to handle this message from past 3 days....



Just please read alll the post and then post dont look the last post and reply back please.....
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Aug 27, 2014 4:10 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

hotrock026 wrote:

Same question will asked by the Consumer , if have an dump of the input Payload i can answer them by showing the message...

If you don't have a valid document the exception list will tell you so. You need to look at the exception list and how you want to return that information in the SOAP Fault information...

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
hotrock026
PostPosted: Wed Aug 27, 2014 4:54 am    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Hi Saper,

See actual requirement is need to dump the incoming payload no one is concern abt the success or invalid payload...
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next Page 2 of 3

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP Input parsing error
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.