ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Parsing failed with Unicode null characters

Post new topic  Reply to topic
 Parsing failed with Unicode null characters « View previous topic :: View next topic » 
Author Message
Angshuman
PostPosted: Tue Jun 25, 2013 3:50 am    Post subject: Parsing failed with Unicode null characters Reply with quote

Apprentice

Joined: 30 Apr 2009
Posts: 29

File parsing is failed with the exception
Quote:
XML parsing error occurred an unicode character is found at the prolog of the document
.
Mainframe system is creating xml and broker is procesing the file
When the broker file input node archives the file to mqsiarchive,seems like unicode character is getting trimmed and when the same file is reprocessed,it is succesful.

Anyone have inputs regarding this?
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Tue Jun 25, 2013 3:54 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Check that the code page + ccsid values are set properly.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
vikas.bhu
PostPosted: Tue Jun 25, 2013 4:00 am    Post subject: Reply with quote

Disciple

Joined: 17 May 2009
Posts: 159

i think CCSID +Encoding?
Back to top
View user's profile Send private message Send e-mail
McueMart
PostPosted: Tue Jun 25, 2013 4:01 am    Post subject: Reply with quote

Chevalier

Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere

Can you inspect the XML file which the mainframe is creating? Use a hex editor to check there arent any strange characters before the first opening tag.
Back to top
View user's profile Send private message
Angshuman
PostPosted: Tue Jun 25, 2013 4:27 am    Post subject: Reply with quote

Apprentice

Joined: 30 Apr 2009
Posts: 29

Just to add to it
WMB is in Unix box. Source system is mainframe.
This issue is occurring sometimes.

Quote:

Can you inspect the XML file which the mainframe is creating?


This is happenning in production, and we are not able to re-create it in lower envrionments.

For failed transaction, we are able to reprocess the archived files from input (mqsiarchive) folder successfully. How is that possible? Does it mean broker truncates the null characters during copy file.
Because of this, we do not have a proof that failure is because of null unicode.
Can someone help please.
Back to top
View user's profile Send private message
Tibor
PostPosted: Wed Jun 26, 2013 3:19 am    Post subject: Reply with quote

Grand Master

Joined: 20 May 2001
Posts: 1033
Location: Hungary

It would be more useful, if you could send the whole ExceptionList tree to the forum (if it was logged).
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Parsing failed with Unicode null characters
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.