Invalid byte 2 of 2-byte UTF-8 sequence JMS Sender CC

[rasjoshi]

Hi Team,

I am getting Invalid byte 2 of 2-byte UTF-8 sequence error at JMS sender Communication Channel.

In CC we have set CCSID - 1208, but still we are getting message failure as we are having special character in payload like this -

ö,ä

Can you please suggest why this error is occurring?

Thanks & Regards,

Rashmi Joshi

[stefan_grube · Accepted solution]

I assume tht the original message inside JMS is not UTF-8.

Check the message with a hex editor and look the codes for the characters and compare with a code page chart.

If the code page is ISO-8859-1, so you have to put 819 as CCSID value.

[rasjoshi · Accepted solution]

Thanks stefan for your reply.

I checked with Message Broker team, Sender is sending message with MessageType 8 --> which is datagram.

Do I need to use CCSID = 819 in my sender jms communication channel?

Thanks & Regards,

Rashmi Joshi

[stefan_grube · Accepted solution]

I checked with Message Broker team, Sender is sending message with MessageType 8 --> which is datagram.

This information is absolutely useless.

Ask for CCSID instead.

[rasjoshi · Accepted solution]

I got reply.. They are using 1208...

Same value I have given in Sender JMS Commu. Channel. Then why message got failed due to special character?

Thanks & Regards,

Rashmi Joshi

[stefan_grube · Accepted solution]

Check the hex code of the character ä and ö. What is it?

[pvishnuvardan_reddy · Accepted solution]

Hi Rashmi,

As stefan suggested, if we check the charset for the two characters, i think it would be ISO-8859-1, which has CCSID as 819.

Can you try with this.

Regards

[rasjoshi · Accepted solution]

If I change CCSID from 1208 to 819 will it be problem for other special characters which XML restrict like ">" "&" etc.

What will happen if any payload comes with these special character? Will message again fail in PI?

Thanks & Regards,

Rashmi Joshi

[stefan_grube · Accepted solution]

Most characters have the same code in UTF-8 and ISO-8859-1. So you should not have any issue with > or &.

Did you check the hex code of ä und ö? Can you tell which code page they are related to?

[rasjoshi · Accepted solution]

Yes hex code for E4 and F6 respectively

Regards,

Rashmi Joshi

[stefan_grube · Accepted solution]

So the encoding is either ISO-8859-1 or Windows 1252.

Try CCSID 819. If this does not work, the CCSID of JMS queue on JMS server has to be changed.

[rasjoshi · Accepted solution]

HI Daniel,

Below is header data, does it help let me know -

<MQMD><SourceQueue>XXXXXXXXX.ENTRY.IN</SourceQueue><Transactional>TRUE</Transactional><Encoding>785</Encoding><CodedCharSetId>1208</CodedCharSetId><Format>MQHRF2 </Format><Version>2</Version><Report>0</Report><MsgType>8</MsgType

Regards,

Rashmi Joshi