Is your machine swapping? 512MB can go quickly...
> -----Original Message----- > From: Sam Gallant [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 14, 2004 3:40 PM > To: Montz, James C. (James Tower) > Cc: Tomcat Users List > Subject: Re: Tomcat 5 pause (free gmail account for fix :-) > > We have done default gc with 8mb/256mb min/max, default gc with > 128mb/256mb min/max, and incremental with the same settings. The > machine has 512mb ram. When we turn on verbose gc the gc logging just > stops after a period of time both on the sun jvm and the ibm. When > there is 100% cpu util jsvc is using 99% of the cpu. > > > On Thu, 14 Oct 2004 14:33:13 -0500, Montz, James C. (James Tower) > <[EMAIL PROTECTED]> wrote: > > Are you defining any Memory Min/Max (-Xms/-Xmx) constraints on the JVM? > > Are you collecting any verbose GC information (-verbose:gc)? > > > > How much physical memory available on the machine? > > > > At times of 100% CPU Utilization, is it java that is consumnig the > > majority of it? > > > > > > > > -----Original Message----- > > From: Sam Gallant [mailto:[EMAIL PROTECTED] > > Sent: Thursday, October 14, 2004 2:17 PM > > To: [EMAIL PROTECTED] > > Subject: Tomcat 5 pause (free gmail account for fix :-) > > > > Everyone, > > Thanks in advance for any help. Also I have a gmail invite for the > > person who has a fix for this if they are interested. > > > > My company has been using Tomcat for several years, but a problem has > > crept up that we have not been able to solve. Basically, tomcat will > > stop processing requests for 2-60 second period several times a day. > > > > Here is a list of software that we have tried. (Note we have tried > > changing each key componant to see if we isolate the componant that is > > the problem, but no luck yet) > > > > OS: RedHat 9 & AS3 > > Threading model: linux threads & nptl > > JVM: sun 1.4.2_4 & latest ibm > > Http connector: ajp w/apache 2 and coyote connector > > JBDC connector 1.0 > > > > 1. Doesn't always happen durning old gen garbage collection, but does > > sometimes > > 2. Before switching to incremental gc we received out of memory errors > > which resulted in Tomcat completly hanging > > 3. After switching to incremental gc the effect changed to 2-60 second > > periods of time that Tomcat won't process request, but it does resume > > on its' own. > > 4. Cpu usage for most of the day is less than 20% utiliztion, but when > > the problem occurs the cpu spikes to 100% utiliztion briefly. > > > > --------------------------------------------------------------------- > > 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]
