File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Java in General and the fly likes Stange UnsupportedEncoding Exception Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Java » Java in General
Bookmark "Stange UnsupportedEncoding Exception" Watch "Stange UnsupportedEncoding Exception" New topic

Stange UnsupportedEncoding Exception

Eddie Howard

Joined: Jul 27, 2006
Posts: 14

I have a very strange problem. Please advise if you can.
I have written a very trival C++ application to integrate by java program with windows OS to run as a service.

Namely I install service, service calls a bat file when started and bat files contain DOS scripting to to start my java program.

While there are better solutions, this solution work fine. I have given this info for background infomation.

Sometime my application must write to an ouptut stream using codepage 437. When it does so I get an "", cannot find cp437 etc. However charset.jar exists in jre lib folder & is specifed on sun.boot.class.path. This only happens when I start run my application from my service.

When I run command from a command prompt, processin of cp437 happens no problem. This there some reason why when running as service, that charsets.jar is not being loaded on classpath?

Is there a separate CLASSLOADER being used somewhere?

I have recently down an upgrade to my application, no changes in upgrade affect encoding etc but before upgrade I had no issues with 437.

I hope problem isn't too vague, if anyone has any suggestion it would really help. I am considering reinstalling jre

Please advise


The men of Ireland were hurling when the gods of Greece were young
Paul Clapham

Joined: Oct 14, 2005
Posts: 19858

Then there's something different in your service setup vis-a-vis your command line. Relative paths relative to a different working directory? Mapped drives referenced in your command line? Using different JREs? You'll have to find out what.
I agree. Here's the link:
subject: Stange UnsupportedEncoding Exception
It's not a secret anymore!