DO NOT REPLY [Bug 6397] New: - Stress testing the server causes a block condition that needs restarting

[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=6397>.
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=6397

Stress testing the server causes a block condition that needs restarting

           Summary: Stress testing the server causes a block condition that
                    needs restarting
           Product: Tomcat 3
           Version: 3.2.3 Final
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Config
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: lacortea2@tiscali.it
                CC: lacortea2@tiscali.it


We are performing a stress test session, using the following architecture:
- Apache JMeter 1.6.1 as the virtual user generator;
- Tomcat 3.2.3 (but the 3.2.4 version is not able to add value on this) as the 
servlet engine;
- Oracle 8.0.5 as the referenced RDBMS (through a custom connection pool);
- CriticalPath InJoin Directory Server 4.0 as the referenced LDAP srv.

During the stress test the number of threads handled by the java virtual 
machine on both Solaris 2.7 and Linux Red Hat (kernel 2.4.16-xfs) is constantly 
growing and leads to a freeze of the entire server. Finally even stopping the 
test generator the threads are not released (a 'ps' command on linux is able to 
show the entire set of these lightweight processes), and the server needs to be 
restarted.

We guess is a simple misconfiguration of the server, but please give an aid 
cause the system is going to be extended to a high amount of users, and this 
trouble is critical. It would be useful to know how to set up the pool of 
concurrent connections entering Tomcat, as well as to know how to control the 
thread management parameters, if any.

Thx, 
Antongiulio La Corte.

PS the same stress test on other apps servers (such as Allaire Jrun) is 
completed with success. However Apache/Tomcat is the preferred solution, if 
feasible.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>