java version "1.2.2"
Classic VM (build Linux_JDK_RC3, green threads, sunwjit)


This is a duplicate of the following Blackdown bug, but only Sun can fix it
since the Blackdown group does not have access to the "sunwjit" source:

  Bug Id 1613, "java.lang.StackOverflowError with sunwjit"
  http://www.blackdown.org/cgi-bin/jdk/incoming?id=1613

I know Sun is using the Inprise "javacomp" JIT in its JDK 1.2.2 RC1 release for
Linux, but Blackdown is still using Sun's "sunwjit" JIT.  Right now, we're faced
with having to tell our customers to download the Blackdown JDK (for fixes to
Blackdown Bugs 1578 and 1604) and then telling them to replace Sun's JIT with
the Inprise JIT for fixes to this bug.

This bug causes the VolanoMark network scalability test to fail the 4,000
connection test.
(Review ID: 98998) 
======================================================================

Use an xxxxx  Just-in-Time Compiler such as the Inprise "javacomp" JIT, or even
IBM's JIT, instead of Sun's JIT.
======================================================================

The sunwjit has been obsolete for long time. We are not going to fix the problem. NOTE: the stack overflow is a fatal user error, it can not be fully recovered on most systems.

 xxxxx@xxxxx  2000-01-03

The problem seems to be some kind of stack related memory leak in sunwjit
which depends on the cumulative number of threads or sockets ever
created in the virtual machine.  This is not a problem with the
concurrent connections but rather with how many connections the Java VM
has ever had since it was started.

Of course, there should be no maximum number of cumulative connections,
and the problem does not occur with the Inprise JIT.

Please see http://www.blackdown.org/cgi-bin/jdk/incoming?id=1613
for details.