Java EE (Java Enterprise Edition) General Discussion

Dear Tomcat � Team!



I�m software developer for web applications (STRUTS) and we are using Jakarta Tomcat (4.1.30 / 4.1.31).



We make performance tests for our web application with the JMeter Tool.



Standard Configuration (server.xml) if you download the Tomcat package.

<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->

<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"

port="8080" minProcessors="5" maxProcessors="75"

enableLookups="true" redirectPort="8443"

acceptCount="100" debug="0" connectionTimeout="20000"

useURIValidationHack="false" disableUploadTimeout="true" />



A configuration (server.xml) with this Tomcat crashes or is not available for a very long time.

<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->

<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"

port="8080" minProcessors="5" maxProcessors="75"

enableLookups="false" redirectPort="8443"

acceptCount="50" debug="99" connectionTimeout="10000"

useURIValidationHack="false" disableUploadTimeout="true" />



We have Tomcat crashes with more than 40, 50, � threads and more. The server is not available for more than 20 minutes.



As you can see we made changes in the server.xml (acceptCount. enableLookups, connectionTimeout, debug). The important attribute acceptCount and connectionTimeout has been changed. If still more simultaneous requests are received, they are stacked up inside the server socket created by the Connector, up to the configured maximum (the value of the acceptCount). Any further simultaneous requests will receive connection refused errors, until resources are available to process them.



Now my question is:

Is the configuration (not standard) the problem that tomcat crashes with more than 40 users?



Thank you in advance.