| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Special Character Issue in MB6.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Senthamizh |
 Posted: Thu Dec 31, 2009 10:01 pm Post subject: Special Character Issue in MB6.1 |
 |
|
Apprentice
Joined: 21 Dec 2009
Posts: 47
|
Hi
My flow has a FileInput Node --> ComputNode --> PublishNode in AIX.
The input message has a speicial Char "°" (degree symbol). While publishing the output xml, it tries to parse the xml and since it is not able to parse this special character, it throws an error.
The same input with special character works well in V5. http://www-01.ibm.com/support/docview.wss?rs=849&context=SSKM8N&dc=DB520&dc=DB560&uid=swg21296565&loc=en_US&cs=UTF-8&lang=en&rss=ct849websphere
I tried using code page 1208, 819, 437, in both properties and MQMD header of the output message. It didn't work.
Since my input was a fileinput node , I also tried using
SET OutputRoot.Properties.CodedCharSetID = InputRoot.Properties.CodedCharSetID
SET OutputRoot.MQMD.CodedCharSetID = InputRoot.Properties.CodedCharSetID
But Nothing worked for me.
The user trace is pasted below
| Code: |
RecoverableException BIP2230E: Error detected whilst processing a message in node 'publish'.
The message broker detected an error whilst processing a message in node 'publish'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
ParserException BIP5010E: XML Writing Errors have occurred.
Errors have occurred during writing of XML.
Review further error messages for an indication to the cause of the errors.
RecoverableException BIP2136E: Source character ''2591'' in field ''003c002f.................................004200750073004'' cannot be converted from Unicode to codepage '819'.
The source character is an invalid code point within the given codepage.
Correct the application or message flow that generated the message to ensure that all data within the message can be represented in the target codepage. |
Any help on this would be much appreciated |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Jan 01, 2010 2:17 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
The error message tells you exactly what is wrong.
I'd like to suggest that you look back at some of the posts on this forum over the past three months which deal with pretty well exactly the same problem you are experiencing.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sat Jan 02, 2010 4:07 am Post subject: Re: Special Character Issue in MB6.1 |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| Senthamizh wrote: |
The input message has a special Char "°" (degree symbol) ...
| Code: |
| RecoverableException BIP2136E: Source character ''2591'' ... cannot be converted from Unicode to codepage '819'. |
|
Source character "2591" is the 'LIGHT SHADE' character (░), not the 'DEGREE SIGN' (°). It does not exist in the ccsid=819 character set.
| Senthamizh wrote: |
| While publishing the output xml, it tries to parse the xml and since it is not able to parse this special character, it throws an error. |
More precisely, this is a conversion error, not an XML parsing error.
There are two different ccsids:- the source ccsid describes the input message. The message flow sets this in the FileInput node properties; it needs to match the coded character set that the sender used to write the file.
- the target ccsid describes the output message; the message flow sets this in Root.Properties.CodedCharSetID.
If the source ccsid is wrong, then changing the target ccsid won't help. |
|
| Back to top |
|
|
| Senthamizh |
| Posted: Tue Jan 05, 2010 2:12 am Post subject: |
|
|
Apprentice
Joined: 21 Dec 2009
Posts: 47
|
Thanks rekarm01
I changed the value of "Message Coded Charetcer set ID" in the 'Input Message Parsing' tab of the FileInputNode to 819 and it worked fine. |
|
| 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
|
|
|
|
