JDK-6778571 : Adjust CompilerThreadStackSize being recognised for backwards compatibility.
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.2,1.4.2_18
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows,windows_2003,windows_xp
  • CPU: generic,x86
  • Submitted: 2008-12-01
  • Updated: 2012-10-13
  • Resolved: 2009-01-12
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.
Other Other
1.4.2_19-rev b07Fixed 1.4.2_21Fixed
Related Reports
Duplicate :  
JDK-6784583 - Compiler thread size leads to issues
Duplicate :  
JDK-6736207 - JVM crash with STACK_OVERFLOW exception
Relates :  
JDK-6579892 - 1.4.2_12 server VM fails with EXCEPTION_STACK_OVERFLOW on Windows in PhaseCFG::set_pinned
Description
For most of 1.4.2's life, the command-line option CompilerThreadStackSize was not recognised on the Windows platform.

In 1.4.2_18 CompilerThreadStackSize is recognised on Windows.  
Some advice exists to use -Xss as an alternative way of getting larger stack for the hotspot CompilerThread.

This no longer works, as was the intention.  

The enhancement request here is to recognise the -Xss (ThreadStackSize) setting for the CompilerThread, IF CompilerThreadStackSize is not being specified.

If implemented, this will mean there is only a small window of update release history in which -Xss does not set the CompilerThread. stack.
Comments
EVALUATION Change logic for recognising stack settings when creating CompilerThread, to recognise -Xss value if CompilerThreadStackSize is not set.
18-12-2008