Jump to content
Excelsior Forums
Roger

Japanese code page MS932 (Shift-JIS)

Recommended Posts

Hi,

A user in Japan just installed our product on their Windows PC which uses Excelsior JET v11.3.

When they start the program it throws the following exception:

Caused by: java.nio.charset.UnsupportedCharsetException: MS932
   at java.nio.charset.Charset.forName(Unknown Source)
   at sun.nio.fs.Util.<clinit>(Unknown Source)

Almost all Windows users in Japan use code page MS932(Shift-JIS) by default.

Here is the full stack trace:

Exception in thread "main" java.lang.ExceptionInInitializerError
   at sun.nio.fs.Util.split(Unknown Source)
   at sun.nio.fs.WindowsFileSystem.<init>(Unknown Source)
   at sun.nio.fs.WindowsFileSystemProvider.<unknown>(Unknown Source)
   at sun.nio.fs.DefaultFileSystemProvider.create(Unknown Source)
   at java.nio.file.FileSystems$DefaultFileSystemHolder.getDefaultProvider(Unknown Source)
   at java.nio.file.FileSystems$DefaultFileSystemHolder.access$000(Unknown Source)
   at java.nio.file.FileSystems$DefaultFileSystemHolder$1.<unknown>(Unknown Source)
   at java.nio.file.FileSystems$DefaultFileSystemHolder$1.<unknown>(Unknown Source)
   at java.security.AccessController.<unknown>(Unknown Source)
   at java.nio.file.FileSystems$DefaultFileSystemHolder.defaultFileSystem(Unknown Source)
   at java.nio.file.FileSystems$DefaultFileSystemHolder.<clinit>(Unknown Source)
   at java.nio.file.FileSystems.<unknown>(Unknown Source)
   at java.io.File.toPath(Unknown Source)
   at javax.crypto.JarVerifier.getSystemEntropy(Unknown Source)
   at javax.crypto.JarVerifier.testSignatures(Unknown Source)
   at javax.crypto.JarVerifier.access$400(Unknown Source)
   at javax.crypto.JarVerifier$1.run(Unknown Source)
   at javax.crypto.JarVerifier$1.<unknown>(Unknown Source)
   at java.security.AccessController.<unknown>(Unknown Source)
   at javax.crypto.JarVerifier.<clinit>(Unknown Source)
   at javax.crypto.JarVerifier.verifyPolicySigned(Unknown Source)
   at javax.crypto.JceSecurity.loadPolicies(Unknown Source)
   at javax.crypto.JceSecurity.setupJurisdictionPolicies(Unknown Source)
   at javax.crypto.JceSecurity.<unknown>(Unknown Source)
   at javax.crypto.JceSecurity$1.<unknown>(Unknown Source)
   at java.security.AccessController.<unknown>(Unknown Source)
   at javax.crypto.JceSecurity.<clinit>(Unknown Source)
   at javax.crypto.JceSecurity.getDefaultPolicy(Unknown Source)
   at javax.crypto.JceSecurityManager.<clinit>(Unknown Source)
   at javax.crypto.Cipher.<unknown>(Unknown Source)
   at javax.crypto.Cipher.getMaxAllowedKeyLength(Unknown Source)
   at com.capitalware.mqve.MQVE.<init>(Unknown Source)
   at com.capitalware.mqve.MQVE.main(Unknown Source)
Caused by: java.nio.charset.UnsupportedCharsetException: MS932
   at java.nio.charset.Charset.forName(Unknown Source)
   at sun.nio.fs.Util.<clinit>(Unknown Source)
   ... 33 more

What can I do to get Excelsior JET v11.3 to support code page MS932(Shift-JIS) ?

Regards,
Roger

 

Share this post


Link to post
Share on other sites

Hi,

I was reviewing options in Jet Control Panel but didn't see anything related. I then went through the options in JetPackII and on the 'Runtime' page I found 'Additional locales and charsets'.  When I expand that list I see 'Japenese Locale' and 'Extended Japanese Charset'.

What is the difference?  Or am I just suppose to include both?

Regards,

Roger

 

 

 

Share this post


Link to post
Share on other sites
13 hours ago, Roger said:

Hi,

I was reviewing options in Jet Control Panel but didn't see anything related. I then went through the options in JetPackII and on the 'Runtime' page I found 'Additional locales and charsets'.  When I expand that list I see 'Japenese Locale' and 'Extended Japanese Charset'.

What is the difference?  Or am I just suppose to include both?

Regards,

Roger

Hello Roger,

You are right, you need to add Japanese locales in JetPackII.

Please add both 'Japenese Locale' and 'Extended Japanese Charset'. It will solve the problem.

 

Share this post


Link to post
Share on other sites

Yes, I did a new build with  'Japenese Locale' and 'Extended Japanese Charset' and gave it to the end-user.  After they installed it, they said everything works now.

 

Regards,

Roger

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×