JDK-4873447 : Compilations killed by concurrent class loading are never recompiled
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2003-06-03
  • Updated: 2004-02-06
  • Resolved: 2004-02-06
Related Reports
Duplicate :  
JDK-4833712 - COMPILE FAILED print out from the debug VM
Description
Running the SunOne Appserver 8.0 with JDK 1.4.2 build 22 and these arguments:
-server -XX:+PrintCompilation
we obeserved that classes that were killed because of concurrent class loading were never recompiled.

Depending on the particular classes that never get recompiled, this could be a significant performance penalty. In the attached print compilation output, some of the non-compiled methods include HashMap.hash and decodeArrayLoop in the NIO decoders.
Comments
EVALUATION ###@###.### 2003-06-16 A spot fix for this does not appear to impact application performance, fix in tiger. ----- Based on the attached output file, the compilation failure precedes the fix for bug 4833712, which addresses this problem (as well as others). There is a very small chance that this bug might still happen, but most such bugs were fixed in mantis FCS by the fix to 4833712. Please reopen or re-submit this bug if the problem still occurs. Note that the new message will say "COMPILE SKIPPED" instead of "COMPILE FAILED". Also, please use the new LogCompilation feature to gather information about the VM's reasons for skipping compiles. http://javaweb.sfbay/~jrose/vm-logging.txt ###@###.### 2004-01-31
31-01-2004