you'll want to max your logging to understand whats going on http://tomcat.apache.org/tomcat-5.5-doc/logging.html I concur with using JConsole *and logging* JMX is good for point in time System wide configuration snapshots If you are doing something like rendering giant PDF's or updating 1000's of records in a DB then you're exhausting resources Try a new TC install and add on one webapp each day.. this way you can at least determine that the last loaded webapp caused the slowdown
Tough to say without more info... M-- ----- Original Message ----- From: "Delian Krustev" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Tuesday, November 27, 2007 2:08 PM Subject: Re: Tomcat becomes non-response for ~30 seconds > On Tue, 27 Nov 2007 10:58:24 -0800 (PST) jnedzel wrote: > > We're having an intermittent problem with Tomcat becoming non-responsive > > for a while (between 30 seconds and several minutes) and then recovering > > without any intervention. There are no error messages in the Tomcat logs. > > > > Any ideas what might be causing this or where to look? > > > > We're running Tomcat 5.5.20 on linux. > > Try running the VM with the -verbosegc option. > May be the garbage collector and the memory settings need some tuning. > > You can also read about JMX and jconsole. They might prove to be helpful. > > Cheers > -- > Delian > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
