Author |
Message
|
praveenmq |
Posted: Mon May 21, 2012 12:27 am Post subject: XML PARSING ERROR |
|
|
 Voyager
Joined: 28 Mar 2009 Posts: 96
|
Hi ,
Am receiving the below error in user.log The request comes from process server to broker.
May 21 11:20:43 stgesb2 user:err|error WebSphere Broker v6105[348380]: (BROKER02.default)[7197]BIP2230E: Error detected whilst processing a message in node 'qa.gov.igov.gsb.channel.http.consumer.MainMF.ForwardToGateway.ProviderChannelFactory.ForwardToEndpoint.ResponseBinding.ApplyBinding'. : BROKER02.c56c3184-2601-0000-0080-fdfc1dcf033b: /build/S610_P/src/DataFlowEngine/ImbComputeNode.cpp: 464: ImbComputeNode::evaluate: ComIbmComputeNode: qa/gov/igov/gsb/channel/http/consumer/MainMF#FCMComposite_1_7.qa/gov/igov/gsb/gateway/ServiceGateway#FCMComposite_1_2.qa/gov/igov/gsb/gateway/ProviderChannelFactory#FCMComposite_1_3.qa/gov/igov/gsb/channel/http/provider/ProviderChannel#FCMComposite_1_3.qa/gov/igov/gsb/channel/http/provider/binding/ResponseBinding#FCMComposite_1_1
May 21 11:20:43 stgesb2 user:err|error WebSphere Broker v6105[348380]: (BROKER02.default)[7197]BIP2488E: (qa.gov.igov.gsb.channel.http.provider.binding.ResponseBinding_ApplyBinding.Main, 5.3) Error detected whilst executing the SQL statement 'DECLARE rEnvelope REFERENCE TO OutputRoot.XMLNSC.soapenv:Envelope;'. : BROKER02.c56c3184-2601-0000-0080-fdfc1dcf033b: /build/S610_P/src/DataFlowEngine/ImbRdl/ImbRdlStatementGroup.cpp: 612: SqlStatementGroup::execute: ComIbmComputeNode: qa/gov/igov/gsb/channel/http/consumer/MainMF#FCMComposite_1_7.qa/gov/igov/gsb/gateway/ServiceGateway#FCMComposite_1_2.qa/gov/igov/gsb/gateway/ProviderChannelFactory#FCMComposite_1_3.qa/gov/igov/gsb/channel/http/provider/ProviderChannel#FCMComposite_1_3.qa/gov/igov/gsb/channel/http/provider/binding/ResponseBinding#FCMComposite_1_1
May 21 11:20:43 stgesb2 user:err|error WebSphere Broker v6105[348380]: (BROKER02.default)[7197]BIP2498E: (qa.gov.igov.gsb.channel.http.provider.binding.ResponseBinding_ApplyBinding.Main, 5.34) : An error occurred when navigating to path element '3' of the field reference at the given location. : BROKER02.c56c3184-2601-0000-0080-fdfc1dcf033b: /build/S610_P/src/DataFlowEngine/ImbRdl/ImbRdlFieldRef.cpp: 1818: SqlFieldReference::navigateAbsoluteToFirst: ComIbmComputeNode: qa/gov/igov/gsb/channel/http/consumer/MainMF#FCMComposite_1_7.qa/gov/igov/gsb/gateway/ServiceGateway#FCMComposite_1_2.qa/gov/igov/gsb/gateway/ProviderChannelFactory#FCMComposite_1_3.qa/gov/igov/gsb/channel/http/provider/ProviderChannel#FCMComposite_1_3.qa/gov/igov/gsb/channel/http/provider/binding/ResponseBinding#FCMComposite_1_1
May 21 11:20:43 stgesb2 user:err|error WebSphere Broker v6105[348380]: (BROKER02.default)[7197]BIP5009E: XML Parsing Errors have occurred. : BROKER02.c56c3184-2601-0000-0080-fdfc1dcf033b: /build/S610_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCParser.cpp: 892: ImbXMLNSCParser::parseFirstChild: :
May 21 11:20:43 stgesb2 user:err|error WebSphere Broker v6105[348380]: (BROKER02.default)[7197]BIP5004E: An XML parsing error 'White space is required between "SYSTEM" and the system identifier.' occurred on line 1 column 15 when parsing element '/Root/XMLNSC'. Internal error codes are '1062' and '2'. : BROKER02.c56c3184-2601-0000-0080-fdfc1dcf033b: /build/S610_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCDocHandler.cpp: 550: ImbXMLNSCDocHandler::handleParseErrors: ComIbmWSInputNode: qa/gov/igov/gsb/channel/http/consumer/MainMF#FCMComposite_1_1
Does the above mean the message passed is not valid??
Or if any changes to the flow will fix it?
Thanks,
Praveen |
|
Back to top |
|
 |
kimbert |
Posted: Mon May 21, 2012 2:04 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
This is the important part of the message:
Quote: |
An XML parsing error 'White space is required between "SYSTEM" and the system identifier.' occurred on line 1 column 15 |
So the XMLNSC parser is saying that it has received a badly-formed XML document. It is probably correct - it is a fully-conforming XML processor.
Is the problem reproducible? What have you tried so far? Do you have a copy of the input document? |
|
Back to top |
|
 |
praveenmq |
Posted: Mon May 21, 2012 2:16 am Post subject: |
|
|
 Voyager
Joined: 28 Mar 2009 Posts: 96
|
Its not like document.
I am just putting some numbers in a text box, with the help of process server communication happens through broker and later it communicates to other part but am seeing this parser error in Broker logs
So is it the message which i put is wrong here? |
|
Back to top |
|
 |
praveenmq |
Posted: Mon May 21, 2012 2:24 am Post subject: |
|
|
 Voyager
Joined: 28 Mar 2009 Posts: 96
|
Yes the problem is reproducable |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon May 21, 2012 3:05 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
you might like to use a tool like Wireshark to look at the raw data being used.
the free version of SOAP/UI can also help here. Setit up as a dummy server. _________________ 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 |
|
 |
kimbert |
Posted: Mon May 21, 2012 3:37 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
Its not like document. |
well...it *must* be an XML document by the time it arrives in your WMB message flow. I would guess that Process Server is constructing an XML document from your text box input.
Quote: |
So is it the message which i put is wrong here? |
well, it depends what you mean. All we know at this point is:
- you are entering some data ( which you have not quoted yet ) into a text box.
- process server is doing something with your data and is then trying to send an XML document to WMB.
- WMB is receiving an invalid XML document ( or thinks that it is )
Back to you for the next step. I think smdavies99's advice is good. |
|
Back to top |
|
 |
praveenmq |
Posted: Mon May 21, 2012 5:53 am Post subject: |
|
|
 Voyager
Joined: 28 Mar 2009 Posts: 96
|
I cant install any tool to the servers.
I also found these in the logs
May 21 16:24:06 stgesb2 user:err|error WebSphere Broker v6105[348380]: (BROKER02.default)[7197]BIP5004E: An XML parsing error 'An invalid XML character (Unicode: 0x48) was found in the prolog of the document.' occurred on line 1 column 1 when parsing element '/Root/XMLNSC'. Internal error codes are '1504' and '2'. : BROKER02.c56c3184-2601-0000-0080-fdfc1dcf033b: /build/S610_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCDocHandler.cpp: 550: ImbXMLNSCDocHandler::handleParseErrors: ComIbmWSInputNode: qa/gov/igov/gsb/channel/http/consumer/MainMF#FCMComposite_1_1
What does the above internal error code mean? |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon May 21, 2012 6:07 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
praveenmq wrote: |
I cant install any tool to the servers.
|
Point the sending app at your desktop?
It is a URL after all...
I'm sure there is a portable version of wireshark. No install needed.
alternatives
Change the input node to read a BLOB. Write the blob to a file. Examine in detail after that. The two ends of the bit of wet string don't agree on something(most likely the format of the message). Be creative in your quest to find out the problem. _________________ 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 |
|
 |
kimbert |
Posted: Mon May 21, 2012 6:07 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
It means exactly what it says : the XML document contains a character that is not legal in an XML document.
This error usually happens when the message flow uses the wrong CCSID to interpret the input XML document. Find out the encoding that Process Server is using to *write* the document, and then set that encoding on the input node in your message flow. |
|
Back to top |
|
 |
rekarm01 |
Posted: Mon May 21, 2012 8:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 1415
|
kimbert wrote: |
This error usually happens when the message flow uses the wrong CCSID to interpret the input XML document. |
Another common problem is that the service is sending an HTML response, rather than XML. |
|
Back to top |
|
 |
|