|
Quick Lists
|
|
Bug ID:
|
4860514
|
|
Votes
|
0
|
|
Synopsis
|
Java hotspot compiler causes runaway process
|
|
Category
|
hotspot:compiler1
|
|
Reported Against
|
hotspot
|
|
Release Fixed
|
1.4.1_05
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
4702051
|
|
Submit Date
|
08-MAY-2003
|
|
Description
|
A problem in the Java JDK 1.4.1 Hotspot compiler causes the Lockhart
console server process to go into an infinite loop allocating heap
memory. Ultimately, the server process consumes swap space and dies.
The Java engineers helping with the investigation suggest this is the
problem reported in bug 4702051.
The original Lockhart reported bug is 4837903.
The problem occurred in JDK 1.4.1_02 on Solaris 9. Lockhart runs
on this JDK in Solaris 8, Solaris 9, and Solaris 10.
It has been suggested that this problem is fixed in JDK 1.4.2.
The problem appears to be related to the JIT compilation of
the Launch$jsp.java class automatically generated by the
Tomcat 4.0.5 Jasper compiler (of the Launch.jsp page).
This generated source file contained 52 finally clauses.
|
|
Work Around
|
Adding the options "-server" provided a work around to the runaway
process.
|
|
Evaluation
|
Compiler problem caused by unlimited jsr inlining. Fix is to add code to
bailout after specified depth. (See bug 4702051).
xxxxx@xxxxx 2003-05-08
|
|
Comments
|
Submitted On 13-MAY-2005
kutts4u
The "-server" option does not help much
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
