DO NOT REPLY [Bug 17481] New: - HotSpot VM Error 11 When Tomcat is load tested.

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17481>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17481

HotSpot VM Error 11 When Tomcat is load tested.

           Summary: HotSpot VM Error 11 When Tomcat is load tested.
           Product: Tomcat 4
           Version: 4.0.6 Final
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Critical
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: eddiew@oakleafconsultancy.com


In completing our performance testing of our web-application running under 
Tomcat we are experiencing the following error:

Unexpected Signal : 11 occurred at PC=0x401bf49a
Function name=scavenge_oop_with_check__8ScavengePP7oopDesc
Library=/usr/local/j2sdk1.3.1/jre/lib/i386/client/libjvm.so

#
# HotSpot Virtual Machine Error : 11
# Error ID : 4F530E43505002C4
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (Blackdown-1.3.1_02b-FCS mixed mode)

After this error all Tomcat processes are terminated.

The first time this happened I reported the bug to both Blackdown and Sun who 
have suggested that it is an application or tomcat problem. As it has now 
happened again and I can find no trace of a problem in our application I am 
raising it here. 

I cannot re-produce (at will) this error but it seems to happen when Tomcat is 
busy - the latest occurence was when we were load testing the system with 40 
users continuously hitting the server (a stress test). 

Reading various forums and posts on the internet this seems to be a common 
problem with people pointing to system resource issues as the root cause but I 
do think this is the case here as we have loads of spare disk and 2Gb of RAM - 
also at the time of occurence the system was not doing anything other than the 
load testing described above.

Has anyone seen this ? Is this is a bug in Tomcat ? Is it a resource issue ? 
Whatever I would appreciate some help as this is causing us serious problems.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org