On 22/12/2009 18:44, Bruce wrote:
Juha,
The problem is fixed. My customer's site has been up for 24 hours with
no problems.
The problem became apparent when I went to the JVM line in
localhost:8080/manager/status. That was showing .5 MB free memory.
I went to the configure Tomcat. I clicked on the Java tab. Set the
"Initial memory pool" at 512. Set the maximum memory pool to 1024.
The program runs fine now.
Monitor carefully, you may just have delayed the problem recurring by
extending the memory available.
"jmap -heap <process_id>" is useful for monitoring the amount of memory
used from the allocated amounts, if it keeps climbing check your
database statements are all properly closed. DB is often the source of
memory leaks.
p
Thank you for your help and suggestions.
Bruce
Juha Laiho wrote:
Bruce wrote:
I have an installation where Tomcat stops every couple hours.
* Tomcat 6.0.18
* Windows XP pro 2.3GHz, 2G memory
* The application is in a .war file.
* This app reads and writes to a MySQL database on the same machine.
What happens is that the application will run for about 3 hours or
so. Suddenly, it stops responding.
A thread dump of the hung Tomcat might well bring more light
to the situation. To me at least this sounds like a thread starvation
issue (for some reason, the request processing threads are not
recycled to serve future requests). The thread dump might well bring
insight as to what the reason might be.
One reason for the starvation might be some deadlock situation across
separate threads accessing the database.
Other things to check are the memory and CPU usage of the hung
Tomcat process - they might also provide some more clues.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
