JDK-4872551 : Cannot control the location of hotspot error log file.
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.2,6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_8
  • CPU: x86,sparc
  • Submitted: 2003-06-02
  • Updated: 2022-05-11
  • Resolved: 2005-07-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b43Fixed
Related Reports
Duplicate :  
Description
An applet is being run using the java plugin (1.3.1_07) with IE 6.0 on win XP. The applet is launched in a browser which was started via a shortcut to IE on the user's desktop. The plugin jvm process crashes outputting the hotspot error log file (hs_err_pidX.log) to the end user's desktop. The log file should not appear on the user's desktop. Need to control where the hs_err_pidX.log file is placed.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
04-08-2004

PUBLIC COMMENTS An applet is being run using the java plugin (1.3.1_07) with IE 6.0 on win XP. The applet is launched in a browser which was started via a shortcut to IE on the user's desktop. The plugin jvm process crashes outputting the hotspot error log file (hs_err_pidX.log) to the end user's desktop. The log file should not appear on the user's desktop. Need to control where the hs_err_pidX.log file is placed.
04-08-2004

EVALUATION A VM flag like -XX:LogFileDir might make sense. Investigate for Tiger. ###@###.### 2003-06-03 Due to the compatibility risk I advise not implementing this feature until the VM logging specification is more complete. Fixing this now introduces yet another command-line option that may not fit into the future logging architecture, but that we will still have to support. ###@###.### 2003-07-10
10-07-2003