| Author |
Message
|
| mqxplorer |
 Posted: Tue Jul 27, 2010 5:32 am Post subject: XML Parsing errors at MQGet node with XMLNSC parser..... |
 |
|
Master
Joined: 22 Jun 2009
Posts: 206
|
Hi All,
I have a strange issue with one of my flows where I am using MQGet node in the reply flow to get the SOAP Reply identifier stored in a queue in the request flow.
The message I am trying to get from the queue is below:
| Quote: |
<SOAP>
<ReplyIdentifier>534f4150060000000000000000000000640b000000000000</ReplyIdentifier>
</SOAP> |
The MQGet node uses the XMLNSC parser to parse the message it is getting from the queue. It is showing a strange sporadic behvior that sometimes the MQGet node does not complain about the message it is getting from the queue and at times it complanins "XML Pasring errors occured". The message MQGet node trying to get is a simple XML message with no namespace involved and I am using XMLNSC parser..WOuld that be a reason for this sporadic behavior?
Thanks in advance... |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Jul 27, 2010 5:46 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| at times it complanins "XML Pasring errors occured" |
Please can you quote the errors, or at least quote the full exceptionList. It's hard to diagnose a problem based on the fact that 'an error has occurred'. I can assure you that message broker has provided a lot more information about the error than you have given us.
| Quote: |
| The message MQGet node trying to get is a simple XML message with no namespace involved and I am using XMLNSC parser..WOuld that be a reason for this sporadic behavior? |
No. XMLNSC doesn't care whether the message has a namespace or not. |
|
| Back to top |
|
|
| mqxplorer |
| Posted: Tue Jul 27, 2010 6:00 am Post subject: |
|
|
Master
Joined: 22 Jun 2009
Posts: 206
|
Below is the error message which I just copied from the event veiwer...
| Quote: |
XML Parsing Errors have occurred.
Errors have occurred during parsing of XML.
XML schema validation error ''Unexpected root tag. Element "SOAP" is not a global element.'' on line '1' column '7' when parsing element ''/Root/XMLNSC''.
Internal error codes: 5032, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according to the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set. |
I do not have any message set specified on the MQGet node.
Thanks in advance.... |
|
| Back to top |
|
|
| mqxplorer |
| Posted: Tue Jul 27, 2010 6:01 am Post subject: |
|
|
Master
Joined: 22 Jun 2009
Posts: 206
|
| One more interesting thing is..I have not experinced this sporadic nehavior with XML and XMLNS parsers specified on MQGet node... |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jul 27, 2010 6:53 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Below is the error message which I just copied from the event viewer... |
Thanks. It's now possible to diagnose your problem 
| Quote: |
| I do not have any message set specified on the MQGet node. |
So you cannot be using validation either...and that suggests that you are probably encountering a defect in the XMLNSC parser.
I suggest that you apply the latest fix pack if you haven't already done so. If you're already on the latest level, or the problem persists after applying the latest level, then a PMR might be the only way to get this sorted. If you do raise a PMR, please reference this thread as context for the IBMer who deals with it. |
|
| Back to top |
|
|
| mqxplorer |
| Posted: Tue Jul 27, 2010 7:37 am Post subject: |
|
|
Master
Joined: 22 Jun 2009
Posts: 206
|
Our broker runtime version is: 6.1.0.7
I am going to open a PMR with IBM and I will reference this thread as a context for the IBMer who deals with it.
Thanks
mqxplorer |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jul 27, 2010 7:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It would be very helpful for whatever IBMer does pick up this PMR if you can identify a particular message to the Input node that drives the MQGet that can cause this issue.
It is likely that there is something in a particular message sent in that is causing this. |
|
| Back to top |
|
|
| mqxplorer |
| Posted: Tue Jul 27, 2010 8:00 am Post subject: |
|
|
Master
Joined: 22 Jun 2009
Posts: 206
|
I have created a demo servcie which replicates my original servcie. I can send the PI file along with the SOAP UI project with which he can test the servcie on his / her desktop. However, this is not a regular problem..It is kind of sporadic. I could re-create this issue by sending continous requests uisng SOAP UI for about one minute by obstructing the flow with the debugger on for sometime where the timeout happens for one exception and let the rest of the requests go through ... Once I craete this issue..It happens very frequently....
Thanks
mqxplorer |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jul 27, 2010 8:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you recreate the issue, and save one of the messages, and restart things or whatever it takes to make the issue go away...
If you only reply that exact message, what happens? Does the issue recur? Or do you have to re-induce it with stress and exceptions? |
|
| Back to top |
|
|
| mqxplorer |
| Posted: Tue Jul 27, 2010 10:12 am Post subject: |
|
|
Master
Joined: 22 Jun 2009
Posts: 206
|
| If you are talking about the request message for the flow..It is the same request I am sending all the time using SOAP UI. I guess, it is not the problem with the incoming request as this sporadic behavior is occurring with the same incoming request. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jul 27, 2010 10:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mqxplorer wrote: |
| If you are talking about the request message for the flow..It is the same request I am sending all the time using SOAP UI. I guess, it is not the problem with the incoming request as this sporadic behavior is occurring with the same incoming request. |
Yes, that's what I was trying to determine - that the sporadic nature had nothing to do with the input message as presented to the Broker. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jul 27, 2010 1:31 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Update : This looks very much like a problem that was discovered and fixed recently in v7 and back-ported into v6.1 under APAR IC66611.
Please
a) raise a PMR requesting this APAR, and
b) make sure that the responder understands that they need to include all code changes made under that APAR. There were several fixes, some of them quite recent. |
|
| Back to top |
|
|
| mqxplorer |
| Posted: Tue Jul 27, 2010 2:34 pm Post subject: |
|
|
Master
Joined: 22 Jun 2009
Posts: 206
|
Thanks a lot Kimbert,
I have raised the PMR. When someone from IBM responds, I will provide this info.
Thanks
mqxplorer |
|
| Back to top |
|
|
|
|
