Mohit Gupta wrote:
I am working on Tomcat 4.1.24 on Solatis-8, 12 CPU, 24GB RAM Machine. I am using Apache 2.0.43 and the Jdk version is 1.4.1_02.
When I start my server then after 5-6 hours my server becomes very slow and then I need to restart my server. I am taking the top stats for the tomcat and have found that normally the thread remains between 100- 140 but when the system crashes it reaches to 372 and the memory gradually increases from 256 to some where around 660. The top stats are as follows
PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND 13082 root 115 0 0 653M 578M cpu/290 313:31 37.64% java 13082 root 139 7 0 654M 579M cpu/291 388:08 40.78% java 13082 root 143 0 0 654M 580M cpu/419 466:39 41.43% java 13082 root 374 1 0 662M 589M cpu/323 547:47 47.03% java 13082 root 374 10 0 662M 589M cpu/291 625:42 53.59% java
Here the Thread count increases from 143 to 374 in just 10 min. Even though the no of user accessing this site has decreased. I really don’t know what the problem is...
I have set the Catalina Option as "-Xms128M -Xmx512M" but even setting the value of -XMx1024 doesn't solved my problem.
The connector settings in my server.xml are as follows
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector" acceptCount="5" bufferSize="2048" connectionTimeout="20000" debug="0" disableUploadTimeout="false" enableLookups="false" maxProcessors="350" minProcessors="5" port="8009" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" proxyPort="0" redirectPort="8443" scheme="http" secure="false" tcpNoDelay="true" useURIValidationHack="false">
<Factory className="org.apache.catalina.net.DefaultServerSocketFactory"/>
</Connector>
Please tell me what is the problem with my configuration. Please help me
First thing to find out is to figure out what all the threads are doing. Send the Tomcat process a -QUIT signal (`kill -QUIT 13082`) and capture the output which will be sent to stdout. You will get a stack trace for each thread showing what it is doing. You will probably find that the threads are busy somewhere in your application code.
Additionally, upgrading to the latest Tomcat (4.1.27 or 5.0.16) and JDK (1.4.2_03) is a good idea as the latest versions have bug fixes and performance improvements.
I doubt it is a Tomcat issue, it is more than likely an issue with your application, but the stack trace will show the cause.
-Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
