| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Base64 Conversion Error |
« View previous topic :: View next topic » |
| Author |
Message
|
| TonyD |
 Posted: Sun Jun 12, 2005 11:42 pm Post subject: Base64 Conversion Error |
 |
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
I have incoming XML messages that contain Base64 encoded file attachments. Mostly this works fine but I have just encountered:
| Quote: |
2005-06-13 17:04:40.580017 4492 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'msPortalXML52'
Message Set Level : '1'
Message Format : 'XML1'
Message Type Path : 'InboundSecureMessageRequest'
Review further error messages for an indication to the cause of the errors.
2005-06-13 17:04:40.580123 4492 ParserException BIP5404E: XML data conversion error.
Error converting characters at position 2617 to logical type 'Binary' in message 'InboundSecureMessageRequest', current element 'http://www.xyz/Messages/Portal/2005/05/PortalXMLSchema_52:FileAttachment'.
Please ensure that the element specified contains valid data for the logical type specified (Binary).
|
A couple of questions:
1. How can I determine which character(s) cause the problem?
2. What is the starting point for 'position 2617' referenced above, as far as the parser is concerned...from the start of the MQMD, the XML declaration at the beginning of the message, or the start of the root element?
Alternatively, here is the problematical attachment:
| Code: |
<FileAttachment>UjBsR09EbGhrQUVzQWZjQUFQLy8vLy8velB2NTdQbjQ5L2IzLy8vL21mLy9NKzd2L3ZEdjdmZm5v
dXprNU9IaC92ZnFjTy9qdjl6ZjQvVFcwdUxaMU5iVy9zelk0dWJmUk5iVzFmcmNFY3pNLzh6TzJP
SEt3c3pNek9iRHBiL0Evc0MvNUwrL3Y4bTlzT083ZE51MnRiQzkwcTY3N2NlNW9iVzEvKzZucUxP
MXQ4R3hrS3VyLzhPeGJweXgwYTJ0cmFpcDE3T29pb091MVBlU2xweXBzNStscEwyYXFtR3U0cG1a
LzNLbXpwbVptYkdXZXU1L2ZJdVlyWTJOL2ZXR0U4eUVncXlSWWNXQ2pvT0UvR21Uc29tS2pPNXZa
WU9HcTN0Ny80U0RnNXQ3VTVwMWZHcDluRzV1LzNkNGVwbHZPVlozbldabS8xOXhlMHB1bm9wbU1t
Wm1abnBrTkN4cG9GSlMvNjlHTmVzMkpFZGFwWDlPUUVaVmtuaFNHRTFWWDBaVGZrSkMvd3Rhb1RC
doRGswNGFLSW9h
aWxTQW5nY2pZd0l5VzdXcDNFUlFFcGJlL0tRZ05oRmRGQzBYSVJvMWhsUlpXVkluMzJXYUl5bXBJ
YnNqWjRGaUJTeGg0Y1ZncFRrZ1BDa0tFbzBROUQyYXN1YnJkamNxZmhvdFdsRUVYWDFTcEsyRElM
U20xOUVCV1Z3am5ZYkFSQWVqT1l4WFlPUVZqSUpPZG9CWmdKVUk1VTRCaFhTbUk1RnBhWWc2a1gy
eU5HZ3VSV2hNaFZVYW0wN3pPcTZ4U1NSUk1NVWtiT0J4UUdXTS8xQVpJMVU1MXNZcEdOSElSOStw
d1pLQkJscGEzY2xhVjFyVm9ibFVkd0U5RTdJaU01bVh4ck93TGZHTjNUeURwOEE1eGl1WldjODl2
NE5RbytaRU5LVGhrRnhKSXREUVpRUXlCYldMaWdoTDF5RHUxV1l1WmVZekcxTlAwVVV6bks2MWdQ
VVNFcFRDR0theGpFRW9ZUDVqMklsS3FMVlJ4Q3hUQlhTY2dheUZPeDRwVHlsZG0xZW5sdGFxVkdM
SzhneXBwQ2o1VXFKaUtpUHNFQXJiTG1Ta0swUmlMSWk4b3Nzb1NXVk5xb1FkWldIaUtDSkFLcTdC
NVZHTUx0SThsbEQzVDJuQ0tsV2JXek9YYnVoL0pRUVhITmFHTGRFU1dESkpUUWtjSE1qV3c5RHhW
eFF4MVdVbW14ckFNR2M4OU9LdFY4QTVGVGMyUVNyZlFyQzRKQ0pMd3Z6cTkyZzluQWpJTnZiRFN3
VnN4WmphNFVocWFERS82a3ZHSWtseDhBSUNBRHM9AA==</FileAttachment>
|
Looks perfectly fine to me! |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jun 13, 2005 3:12 am Post subject: Re: Base64 Conversion Error |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| TonyD wrote: |
| 2. What is the starting point for 'position 2617' referenced above, as far as the parser is concerned...from the start of the MQMD, the XML declaration at the beginning of the message, or the start of the root element? |
I'm going to say that you should start counting at the first byte in the body of the message - immediately after the end of every header.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jun 13, 2005 4:29 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Alternatively, you could find out what the starting point is by deliberately introducing an error at a known point - say, at the start of the element which fails. For instance, you could convert the opening tag of FileAttachment into a closing tag, causing the XML document to be badly-formed at that point. Even better, you could deliberately insert a bad character at the start of the base64 data, if you know what a bad character looks like (I don't). |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
