What kind of activity is going on with this server during those two
hours?  Heavy, moderate, light load?  Is it a development box or
production?

I ask the last question, since some have seen a problelm with repeated
redeploys of a web application, where the JVM's "permanent generation"
memory is running out even though the rest of the memory pools are
nowhere near full.

Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com

>>> [EMAIL PROTECTED] 3/25/04 5:50:42 PM >>>
We have Tomcat 4.1.27 running in conjunction with Apache 1.3.x. We're 
using AJP13 connector. The machine that we're using has got over 2GB of

Memory and good processor speed. Tomcat has been allocated 1 GB of max

memory.

The issue is: For every two hours or so Tomcat hangs. That means, 
Tomcat don't crash but simply don't accept any more connections. While

using Tomcat with Apache we're getting "500 Internal Server Error". We

are constantly restarting server to make it work. There is no good 
information in the logs that could lead us to debug this issue.

I have tried several things. Taken out Apache and Connectors from the 
equation by running Tomcat as standalone. This time Tomcat we 
get "server not found error - Page cannot be displayed" message. I have

also increased the maxProcessors of the connector to 300 instead of the

default 75.

Interesting thing is -- when Tomcat hangs the memory usage never 
reaches even half of the max memory (1 GB) allocated to Tomcat, and the

number of threads that we see is also always less than half of 
maxProcessors value (300) set. 

If anybody encountered this kind of issue or if you have any thoughts 
please respond.

Thanks in advance!

- SPS



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED] 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to