Comments on: Description of Java hs_err error log files

By: hs_err decyphered… the followup at stotti.blog()

hs_err decyphered… the followup at stotti.blog() — Wed, 15 Apr 2009 20:16:00 +0000

[...] [update] This information is related to developers only. If you have Java problems or want to know more about hs_err errror logs please refer to this more general post.[/update] [...]

By: stotti

stotti — Fri, 10 Apr 2009 12:43:48 +0000

Thanks for the reply, Jeff. Sorry to answer you this late.

In Java versions before 1.5 (such as v1.4.2) the JVM writes error logs to the current working directory of the application. So please check if the working directory of your app is the desktop, i.e. the application is being started from there.

If the current directory is not writable the hs_err log is saved to the system temporary directory, which may be identified by a call to System.getProperty(”java.io.tmpdir”); If this method returns the desktop location, you could try to set it by calling System.setProperty(”java.io.tmpdir”, “C:\temp\”); directly from your code – if you have control over the legacy app. Otherwise try setting the global path for temporary files via Windows.

Please comment again when it worked out or you need assistance.

Best wishes
Stotti

By: Jeff

Jeff — Sat, 28 Mar 2009 22:17:39 +0000

1.4.2_12. Unfortunately, a legacy piece of software requires that we not update to anything newer.

By: stotti

stotti — Wed, 25 Mar 2009 23:58:50 +0000

Hi Jeff, can you please state the Java version you are using? The flag depends on the JVM version.
Please comment again and I’ll see if I can help you out.

Best regards
Stotti

By: Jeff

Jeff — Wed, 25 Mar 2009 22:45:28 +0000

How would you recommend preventing these files from appearing on a user’s desktop, or forcing the file to go to an out of the way location? I’m running Windows machines where this is happening.

I’ve added to the runtime parameter: -XX:ErrorFile=C:\TEMP\hs_err_pid.log, but it didn’t seem to have any effect.