Tomcat Process Memory Leak?

2007-12-14 Thread Bill Clarke-Fields
Hi All, I am looking for some help. We are running into what appears to be a memory leak situation. The Java heap usage looks fine, but the overall Tomcat process memory usage continuously goes up and up, until it reaches the Windows 2GB per process limit, at which point it crashes. Using the

RE: Very Long Full GC after Inactivity

2007-10-09 Thread Bill Clarke-Fields
, -Bill Peter Crowther wrote: From: Bill Clarke-Fields [mailto:[EMAIL PROTECTED] We are running an application on Tomcat 5.0.28 with Java 1.4.2. The usage of the application is very cyclical. It is used heavily during the day, and lightly at night. During peak daytime hours, a full

Very Long Full GC after Inactivity

2007-10-08 Thread Bill Clarke-Fields
Hi, We are running an application on Tomcat 5.0.28 with Java 1.4.2. The usage of the application is very cyclical. It is used heavily during the day, and lightly at night. During peak daytime hours, a full garbage collection takes less than 2 seconds, which is fine. However, after a long

Re: Very Long Full GC after Inactivity

2007-10-08 Thread Bill Clarke-Fields
given to jvm startup). Server and client mode have different GC mecanisms. Bill Clarke-Fields a écrit : Hi, We are running an application on Tomcat 5.0.28 with Java 1.4.2. The usage of the application is very cyclical. It is used heavily during the day, and lightly at night. During peak

RE: Very Long Full GC after Inactivity

2007-10-08 Thread Bill Clarke-Fields
Charles, I have tuned the heap size based on what is ideal during peak hours. The problem is that off-hours usage is very different, and leads to these very long full GCs. Does it sound like an application problem? I have not done any analysis to determine what kind of objects are hanging

RE: Very Long Full GC after Inactivity

2007-10-08 Thread Bill Clarke-Fields
: From: Bill Clarke-Fields [mailto:[EMAIL PROTECTED] Subject: RE: Very Long Full GC after Inactivity The problem is that off-hours usage is very different, and leads to these very long full GCs. GC pause time is largely dependent on the number of live objects existing at the time of the GC, so