| Author |
Message
|
| dutchman |
 Posted: Fri Mar 08, 2002 3:13 am Post subject: |
 |
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Dear all,
I have a largish file (about 760K) with XML data in it.
Utility MQSIPUT is used to add it as a single message
to an MQSeries queue,and then I parse it via MQSI V202 (CSD2).
The input file to MQSIPUT had to be amended to have
MESSAGELENGTH 775000.
Unfortunately, it gets rejected with an XML parser error :
<snip>
( MQSIBK1.default ) An error has been reported by the BIPXML4C component:
code '65601'; public id ''; line number '1'; column number '349716';
current element 'abc'; error text 'Unterminated entity reference'.
The above error was reported by the XML parser.
Check that the XML message is well-formed and that it adheres to the XML specification.
<endsnip>
I'm wondering if MQSIPUT is in fact able to put the whole message.
If it didn't, then that would explain the error saying that it
may not be 'well formed'.
Has anyone else seen this before? Is there a limit to what
MQSIPUT can handle? |
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Mar 08, 2002 10:38 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hi,
I guess there is a message size limit for MQSIPUT utility. You could try sending an email to Author of the utility to get this clarified.
Alternatively, you can try using supportpac IH03 from url http://www-4.ibm.com/software/ts/mqseries/txppacs/ih03.html to test your message flow.
If you are not setting lots of MQMD fields in your test, you could even write a C program which does the same thing.
Regards,
Kiran
|
|
| Back to top |
|
|
| dutchman |
| Posted: Mon Mar 11, 2002 2:17 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Thanks. I found the problem. I was scanning the XML message for particular attributes. One of them contained this :
<Message desc="--> this is the data" date="11Mar2002" etc />
The parser got confused with the '>' within the desc attribute.
The thing is that I'm not actually looking for this attribute, but the ESQL
probably causes it to examine each attribute.
Other than changing the contents of this attribute, I don't know how to fix this. I was expecting the parser to ignore this character because it is inside
quotes. |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Tue Mar 12, 2002 2:08 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
If I am not wrong, your > within the quotes should be >. You might run into troubles with other applications using > in values.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| Back to top |
|
|
| dutchman |
| Posted: Tue Mar 12, 2002 2:34 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Jan - thanks, but I have no control over what is put in the description field. Think of it this way: customer has a GUI where they can enter freeform text. This is stored as an attribute, eg desc="bla bla bla".
I then have a Compute node that wants to pick up other attributes. Unfortunately, I think the parser goes through byte-for-byte an 'sees' the character '>' as a eng-tag.
I agree with you that the program should store it as >.
Again, I expected the character '>' - when it's embedded within quotes - to be ignored.
Any other thought? ... regards/groetjes ... Ruud |
|
| Back to top |
|
|
| Cliff |
| Posted: Tue Mar 12, 2002 3:36 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Ruud,
is it possible to get the GUI to translate > into > when writing the data?? Not ideal, I know, but a possible workaround.
Cheers - Cliff |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Tue Mar 12, 2002 5:57 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
Ruud,
I did some digging for you in XML docs. Single markup elements are not allowed in the text. So the quotes don't have anything to do with it, the '>' is not allowed there and should be a '>'. As a result, the XML which troubles you is not well-formed.
As cliff wrote, the application building this XML should translate the '>' in '>' (as well as the other markup elements, & < > " and ').
note1! The " in your attributes are the markup quotes, these should be left as-is. These are needed to distingues the difference between a space in an attribute value and the delimiter of an attribute.
note2! I forgot the ; in my previous posting, this is mandatory.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| Back to top |
|
|
|
|
