| Author |
Message
|
| jagan |
 Posted: Mon Jul 16, 2007 1:46 pm Post subject: An error has been reported by the BIPXML4C component |
 |
|
Acolyte
Joined: 26 Jun 2001
Posts: 55
|
Getting the "An error has been reported by the BIPXML4C component." error when trying to copy the XMLNSC message into the OutputRoot element. This exception is not coming every time only some time this is coming. I have been runing same input message every time for the testing 10 out of 4 times this exception is coming.. No sequece i have observed some time every thing will go some time nothing.. no pattern for this exception..
the code is as below
In the Message flow at certain condition iam storing the InputRoot.XMLNSC into the Environment variable and using that after some time alter
Create LastChild of Environment.Value DOMAIN('XMLNSC');
Set Environment.Value.XMLNSC = InputRoot.XMLNSC;
Iam getting the exception only some time while the below statement
SET OutputRoot.XMLNSC=Environment.Value.XMLNSC;
the exception is throwing while assigning the OutputRoot.XMLNSC, checked the values stored each time in the Environment but every time the values are same..
IF any one have similar issues please share.. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jul 16, 2007 1:58 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What is the BIP number with the exception?
What is the error message?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jagan |
| Posted: Mon Jul 16, 2007 2:09 pm Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 55
|
| jefflowrey wrote: |
What is the BIP number with the exception?
What is the error message? |
5004 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jul 16, 2007 2:13 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So you read
| Quote: |
BIP5004
Severity
20 : Error
Message
An XML parsing error '<insert_4>' occurred on line <insert_2> column <insert_3> when parsing element '<insert_5>'.
Internal error codes : '<insert_0>', '<insert_1>'.
Explanation
This error was reported by the generic XML parser. It is usually the result of a badly-formed XML message.
Response
Check that the input XML message is a well-formed XML message that adheres to the XML specification. Note that the line number and column number quoted give the position where the parser discovered the problem. The actual error might be earlier in the message.
Other possible causes could be:
1. A character not supported by XML in the instance message data.
XML only supports a subset of control characters so ensure that no unsupported characters, such as X'00', appear in the document.
2. The Coded Character Set ID defined in the message header does not reflect the contents of the instance message.
If the XML document has an XML prologue, the WebSphere MQ CodedCharSetId should be consistent with the XML Encoding field.
3. A reserved XML character appears in the instance message data.
Characters that could otherwise be recognised as XML mark-up such as < or & should be replaced with the comparable XML entities such as < or &. |
?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Mon Jul 16, 2007 2:21 pm Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
If you are getting this error in 4 out of 10 messages, please check if you have another instance of the flow running on the broker.
Cheers, |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jul 17, 2007 12:25 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| the exception is throwing while assigning the OutputRoot.XMLNSC |
The exception is being thrown by the XMLNSC parser while it is parsing the input bitstream. The parsing does not happen until this line is executed because Parse Timing is set to 'On Demand' on the input node.
Please post details of your message flow. I suspect that XMLNSC is seeing a different input bitstream or different message properties each time. |
|
| Back to top |
|
|
| jagan |
| Posted: Tue Jul 17, 2007 8:40 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 55
|
| kimbert wrote: |
| Quote: |
| the exception is throwing while assigning the OutputRoot.XMLNSC |
The exception is being thrown by the XMLNSC parser while it is parsing the input bitstream. The parsing does not happen until this line is executed because Parse Timing is set to 'On Demand' on the input node.
Please post details of your message flow. I suspect that XMLNSC is seeing a different input bitstream or different message properties each time. |
thnaks for all the inputs.. Will check the same once again and post with details |
|
| Back to top |
|
|
| bradhack |
| Posted: Wed Aug 01, 2007 8:12 am Post subject: |
|
|
Newbie
Joined: 28 May 2002
Posts: 7
|
Have you found a resolution for this error? We are seeing the same sporadic results trying to build an XMLNS output structure from an environment variable that has an XMLNS domain.
Once we see the issue, subsequent messages will consistently generate the bip5004 error until we recyle the execution group, and then identical messages all will process fine for a time.
I'm wondering if you are on FixPack4 of WMB v6? It seems that we started to see this issue once we applied that fixpack. I know it has since been revoked by IBM so I'm proposing to revert to fixpack3 and apply some necessary hotfixes. I'm quite confident that we had this working for months, but was just curious to see if anyone coded an alternate solution. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 01, 2007 2:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you tried instead:
| Code: |
create lastchild of OutputRoot domain ('XMLNSC');
Set OutputRoot.XMLNSC = Environment.Value.XMLNSC; |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bradhack |
| Posted: Mon Aug 06, 2007 7:52 am Post subject: |
|
|
Newbie
Joined: 28 May 2002
Posts: 7
|
| Using XMLNSC does seem to have worked. I understand that it compacts the tree structure and reduces memory, but I can't believe that was the cause of the intermittent issue where the environment variable would disappear. Especially when other environment varibales that did not contain the original tree were still present. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Aug 07, 2007 12:24 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
BIP5004 is reported by the XML scanner when the input document is badly-formed. Please quote the full text of the error.
If you are certain that this is a regression between FP3 and FP4 you should raise a PMR. But first, read the error message and check very carefully that the problem is not in your message flow. |
|
| Back to top |
|
|
|
|
