The VM crashes on Linux and Windows with
-XX:CompileThreshold=200 and the following method (class attached) causes a
      
crash of the JVM com/sapportals/portal/prt/jndisupport/util/
AbstractHierarchicalContext

lookup The crash happens on Windows and Linux (both x86), other platforms
not tested. Excluding this method from JIT seems to prevent the crash. On
Windows, the crash seems to be reproducible all the time with the following
 

Java Error ID: # Java VM: Java HotSpot(TM) Server VM (1.4.2_05-b04 mixed
      
mode) # # Error ID: 4255494C442F4F502D41500E4350500107 # # Problematic Thread:
prio=1 tid=0x08b5aa18 nid=0x3f54 runnable also see attached Windows_crash.txt
 
for crash transcript. The JVM on Linux sometimes crashes with the above
      
error id, sometimes it crashes without error id. Please see the attached
Linux_crash.txt transcript.
###@###.### 10/14/04 16:41 GMT



------------------------------------------
Please pull the Dr. Watson dump from
http://sap-jtc.germany.sun.com/transfer/cr6179233/20041014

Stefan Schneider
###@###.### 10/15/04 00:40 GMT
------------------------------------------
Three other crash scenarios are shown here:

http://sap-jtc.germany.sun.com/transfer/cr6179233/20041018/crash1
http://sap-jtc.germany.sun.com/transfer/cr6179233/20041018/crash2
http://sap-jtc.germany.sun.com/transfer/cr6179233/20041018/crash3

The files from each of these crashes are attached as follows:

Crash 1: AbstractHierarchicalContext.java, Windows_crash.txt and Linux_crash.txt
Crash 2: WSConfigurationHandler.java
Crash 3: PortalServiceItem.java
###@###.### 10/19/04 16:26 GMT

------------------------------------------

The customer has hinted that excluding PortalServiceItem.startServices from compilation avoids all failures. We are hoping for confirmation of this workaround.
###@###.### 10/19/04 16:27 GMT