Please see app server bug 4757880.

             Am able to reproduce the problem on Linux Sep15 release.

             The appserver startes and appservd processes start the JDK. When the SpecJ is
             run, the JDK dies with SIGSEGV (segmentation fault - invalid memory reference).

             The deamon process captures all the signal handlers and handles SIGSEGV in the
             default manner (print and error message). It then detects that the child process
             has crached and restarts the JVM.

             Since the child prcess here is the JVM, I havent explored what causes the
             problem. It is suffice to say that under stress the JVM crashes. To further
             prove this theory, I tried replacing the JVM with an older one (1.4.0). On this
             JVM I am able to get the results of the benchmark.

             Again switching to JDK 1.4.0_02 make the appserver crash. I havent tried with
             JDK 1.4.0_01 and would be as soon as I find the bits.

             This is clearly a JDK issue under load.

             Also woul dbe testing on 1.4.0_03 to confirm this as 1.4.0_03 is slated to be
             the JVM we would be shipping.

             This Bug arises only on JDK version 1.4.0_02 for Linux.

---
Due to 4741681 and 4629175 App server will probably need to certify on 1.4.1 (or maintenance release)


Mon Oct 07 10:42:50 MDT 2002 tsteele@litehouse

Mon Oct 07 21:20:18 MDT 2002 sm119578

a