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 » IBM MQ Java / JMS » Corrupted chars

Post new topic  Reply to topic
 Corrupted chars « View previous topic :: View next topic » 
Author Message
fredand44
PostPosted: Tue May 16, 2006 10:49 pm    Post subject: Corrupted chars Reply with quote

Acolyte

Joined: 14 Feb 2006
Posts: 63
Hello!

We send a TextMessage from Weblogic 8.1 (over a Messaging bridge in WL) to a Queue at MQ. The messages at the queue is later consumed from a app at WebSphere.

The text is in fact a XML-structure. Unfortunately it may contain swidish signs like [code]åäö[/code]. These chars is corrupted when the message is processed at WebSphere.

Some where along the way the chars get corrupted. Unfortunately I can not say exactly where the corruption takes place, but I guess it is at MQ.

So now is my question if any one got some hints how to solve this.

Best regards
Fredrik
Back to top
View user's profile Send private message
fredand44
PostPosted: Wed May 17, 2006 11:23 am    Post subject: Perhaps a clue!!! Reply with quote

Acolyte

Joined: 14 Feb 2006
Posts: 63
Hello!

Hopefully this is some clues.
The text inside the message is a xml-string. The xml got this encoding:
<?xml version="1.0" encoding="UTF-8"?>
or we have also tried with
<?xml version="1.0" encoding="ISO-8859-1"?>

Acctually we do not think thiss matters since this is "folded" inside a JMS TextMessage.

We have there for also set this (both utf-8 and iso-8859-1) on the protocol iiop at the server inside WebLogic.

When the message is send we write the xml to file and everything looks fine:

SalesItemLegacyId="ÅÄÖåäöÅÄÖ"

Hopefully you are able to se the chars, in case I have html-encode them like:
&Aring;&Auml;&Ouml;


How ever when the message reach MQ it looks like and we browse the queue the messsage looks like:

001D0 42 75 6E 64 6C 69 6E 67--3D 22 22 20 53 61 6C 65 |Bundling....Sale|
001E0 73 49 74 65 6D 4C 65 67--61 63 79 49 64 3D 22 C3 |sItemLegacyId..+|
001F0 85 C3 84 C3 96 C3 A5 C3--A4 C3 B6 C3 85 C3 84 C3 |.+.+.+.+.+.+.+.+|
00200 96 22 20 53 61 6C 65 73--49 74 65 6D 4E 61 6D 65 |...

And if we browse it with a client tool it looks like:

SalesItemLegacyId="ÅÄÖåäö"

Inside MQ it looks like the "code set"/"page set" is set to 437 or IBM-437 (I hope I put that right since I am at home now).

Our gues is that IBM-437 and UTF-8/ISO-8859-1 give us a missmatch.

So if any one know how to solve this please let us know!

Best regards
Fredrik
Back to top
View user's profile Send private message
fredand44
PostPosted: Mon May 22, 2006 6:41 am    Post subject: Answer? Reply with quote

Acolyte

Joined: 14 Feb 2006
Posts: 63
Hello!
Thanks for all help, but we solved it by using BytesMessage instead.

We do not know why TextMessage or ObjectMessage result in corrupted chars.

Best regards
Fredrik
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 » IBM MQ Java / JMS » Corrupted chars
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.