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 6704] New: - rmi client in jsp causes port down after large amount of requests
Date Wed, 27 Feb 2002 07:03:14 GMT
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=6704>.
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=6704

rmi client in jsp causes port down after large amount of requests

           Summary: rmi client in jsp causes port down after large amount of
                    requests
           Product: Tomcat 3
           Version: 3.3 Final
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: hughjlee@yahoo.com


jdk version: 1.3.1

we write rmi client in jsp. the client calls lookup method, then one rmi 
method, which on server side simply prints a count to console and returns 
immediately. testing using microsoft web stress tool with either multi-thread 
or single-thread, the server port (8080 by default) becomes not accessible 
after about 100,000 requests. the rmiregister, rmi server and tomcat are all 
ok, but the port 8080 is down, and tomcat needs to be restarted.

we move the same rmi client code to servlet, test millions of request with web 
stress tool, everything is ok.

this bug is reproducible. we also test it on an aix system and the port becomes 
not accessible merely after thousands of requests.

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


Mime
View raw message