| Author |
Message
|
| arunsenthild |
 Posted: Tue Jan 08, 2008 9:31 am Post subject: MQJMS1046:The character set Cp437 is not supported(Diff pbm) |
 |
|
Novice
Joined: 24 Dec 2007
Posts: 11
|
Hi all,
I know if we reinstall JVM with international support option this problem will go, but this problems looks different.
I have two queues, if i put message in one queue this error happens.
if i put message in another queue of the same queue manager it is geting processed successfully without any of such error.
Pl help me out solving this issue.
Many thanks in advance.
Arun. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Jan 08, 2008 1:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Different CCSID setup in the JNDI layer for the queue perhaps ??
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| arunsenthild |
| Posted: Wed Jan 09, 2008 12:59 am Post subject: |
|
|
Novice
Joined: 24 Dec 2007
Posts: 11
|
I tried putting the message directly in the queue using put message even though i get this same problem.
pl tell me how to solve this issue.
Also i found out charsets.jar in jre\lib folder was missing, so i copied it and put it the corresponding folder. Still the problem exists.
Many Thanks in advance.
Arun |
|
| Back to top |
|
|
| atheek |
| Posted: Wed Jan 09, 2008 2:10 am Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
| This Unsupported encoding exception generally tends to be a jvm issue...Are you using the same jvm environment to post to the 2 queues? Also what is your jre version? In versions prior to 1.4.2, I think you need to use i18.jar for getting support for cp437 |
|
| Back to top |
|
|
| arunsenthild |
| Posted: Wed Jan 09, 2008 3:04 am Post subject: |
|
|
Novice
Joined: 24 Dec 2007
Posts: 11
|
the jre version i'm using is 1.4.2 only.
now if i send the message from some other system the message stays in the backup queue. the message data is in some other language.so that it is not getting processed.
pl tell me how to solve this pbm.
The previous pbm got solved after the queue manager is restarted. (ie) by putting message directly in the queue.
Many thanks in advance. |
|
| Back to top |
|
|
| atheek |
| Posted: Wed Jan 09, 2008 4:01 am Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
| So are you still getting the unsupported character set exception? can you do an "amqsbcg" and find out what values are set for the following fields FORMAT, ENCODING and CodedCharSetId in MQMD Headers for the messages in the queue? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jan 09, 2008 4:27 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If this is a JMS Text message MQ will attempt the get with Convert (equivalent in base java is the get with convert option set)
If the CCSID set on the qcf/tcf object (qmgr object in base java) does not allow for a conversion you might get this exception.
Remember that by default this value is the value of the CCSID on the qmgr you are connected to...
My suggestion would be to set either CCSID 1208 (UTF-8 ) to the qcf/tcf (qmgr) object or CCSID 1200 Unicode.
I have seen this type of problem mostly when there is no conversion for a special character in the target CCSID.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
