Posted: Mon Jun 02, 2008 11:01 pm Post subject: Encoding problem in Message Flow.
Newbie
Joined: 02 Apr 2008 Posts: 8
Hello,
I have message flow which is using Database node.
MQInput -> Database -> MQOutput
This database node is connected to MS SQL Server 2005 and executes stored procedure. This procedure returns answer in Georgian language: eg "ÞÅÄËÉ ÈÀÒÉÙÉÈ ÓÀÁÖÈÉÓ ÂÀÔÀÒÄÁÀ ÀÒ ÛÄÉÞËÄÁÀ" - (NOT UNICODE)
When message flow tries to write message in MQOutput node i have error and message is rolled back in to MQInpute node.
I have next error in eventviewer:
Event Type: Error
Event Source: WebSphere Broker v6006
Event Category: None
Event ID: 2136
Date: 6/2/2008
Time: 6:53:09 PM
User: N/A
Computer: RESEARCH_WMSRV1
Description:
( TestBroker.execGroup ) Source character ''d300'' in field ''64006f0063005f0064006100740065005f0069006e005f0064006f0063003e0032003000300038002d00300035002d00330030003c002f0064006f0063005f0064006100740065005f0069006e005f0064006f0063003e000a00200020003c0064006500700074005f006e006f003e0033003c002f0064006500700074005f006e006f003e000a00200020003c00700072006f0064005f00690064003e0034003c002f00700072006f0064005f00690064003e000a0020003c002f0041006400640044006f0063003e000a0020003c0052006500730070006f006e00730065003e000a00200020003c00530051004c00530054004100540045003e00340032003000300030003c002f00530051004c00530054004100540045003e000a00200020003c00530051004c0043004f00440045003e002d0031003c002f00530051004c0043004f00440045003e000a00200020003c00530051004c004500520052004f00520054004500580054003e005b004d006900630072006f0073006f00660074005d005b00530051004c0020004e0061007400690076006500200043006c00690065006e0074005d005b00530051004c0020005300650072007600650072005d00d300c400d300e100c900d3002000c800c000cd00e100c0002000cd00c000ca00cb00c400c100c900c0002000cd00cf00cb00c600c4003c002f00530051004c004500520052004f00520054004500580054003e000a00200020003c00530051004c004e00410054004900560045004500520052004f0052003e00350030003000300030003c002f00530051004c004e00410054004900560045004500520052004f0052003e000a00200020003c0052006500730070006f006e00730065004d006500730073006100670065003e005b004d006900630072006f0073006f00660074005d005b00530051004c0020004e0061007400690076006500200043006c00690065006e0074005d005b00530051004c0020005300650072007600650072005d00d300c400d300e100c900d3002000c800c000cd00e100c0002000cd00c000ca00cb00c400c100c900c0002000cd00cf00cb00c600c4003c002f0052006500730070006f006e00730065004d006500730073006100670065003e000a00200020003c0052006500730070006f006e007300650043006f00640065003e002d0031003c002f0052006500730070006f006e007300650043006f00640065003e000a0020003c002f0052006500730070006f006e00730065003e000a003c0052006500730070006f006e00730065002f003e003c002f0058004d004c0052006f006f0074003e00'' cannot be converted from unicode to codepage '437'.
The source character is an invalid code point within the given codepage.
I don't understand why Message Broker writes "cannot be converted from unicode to codepage '437'" because I have no unicode characters in this message..
You have to understand a few things about CCSID.
First how are you storing the data in MSSQL (what CCSID/codepage is it in?)
Second how are you retrieving that data. I would imagine as a BLOB that you then need to transform to char specifying the CCSID. (Is the ccsid of the data (BLOB) stored in the DB?)
Finally having the data in the correct format for the broker to understand, you need to know that the broker's internal representation is Unicode (ccsid 1200). This means that not all characters are convertible to a CCSID like 437. Try sending the message in UTF-8 or CCSID 1208...
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