tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30052] New: - JSVC instability
Date Mon, 12 Jul 2004 14:05:58 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30052>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30052

JSVC instability

           Summary: JSVC instability
           Product: Tomcat 5
           Version: 5.0.25
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Native:Integration
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: davidw@gpsoft.co.uk


Start the tomcat web server with jsvc and then run at least two simultaneous 
client web sessions with some (complex) java processing. The JVM soon crashes 
with what looks like a glibc incompatibility. This crash never happens when 
running without jsvc.

Notes:

The same behaviour happens with Server port 80 or client port 8080 (port 80 
without jsvc is not possible).

The same behaviour happens with (Tomcat4 and Tomcat5) 
org.apache.catalina.connector.http.HttpConnector and with
org.apache.coyote.tomcat4.CoyoteConnector and with
org.apache.coyote.tomcat5.CoyoteConnector

The same behaviour happens with Redhat Linux versions 7, 8 and Fedora

The same behaviour happens on two different (Compaq) server machines

This bug is a blocker because it prevents production use where server security 
is vital.

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


Mime
View raw message