-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All,
On 2/22/2010 2:14 PM, Peter Crowther wrote: > On 22 February 2010 19:07, Caldarale, Charles R > <chuck.caldar...@unisys.com> wrote: >> Sounds like the OS might be paging out Tomcat, and taking a long time to get >> all the necessary pages back in when a request is made. I'm not familiar >> with operational details of AIX, but I would suspect there are some >> system-level monitoring tools available to see if there is a paging spike in >> this situation. > > vmstat > (http://publib.boulder.ibm.com/infocenter/aix/v6r1/index.jsp?topic=/com.ibm.aix.cmds/doc/aixcmds6/vmstat.htm) > would do the job. No finesse, but sufficient information :-). +1 If Tomcat/JVM is being swapped-out or otherwise passivated, a simple "are you alive" script can be scheduled to run at intervals to keep Tomcat in memory. Something like every hour or maybe every minute, you could make a request to some trivial page like "/ping.jsp". Another possibility is that your webapp uses database connections which are becoming stale during these periods of inactivity. Oracle, specifically, is well-known for taking a long time to re-establish a database connection, so it's possible you're waiting for that to happen after these idle times. Several solutions are possible, including: 1. Use the ping.jsp technique to also issue a trivial query against the database 2. Change your database connection configuration to allow for longer idle times - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuEJwEACgkQ9CaO5/Lv0PDZCwCeM8Yc259GpiqPB/KkgotGdBVL epsAoID+/TlQ8FQSB4/4LpKLIsKewfhT =EuRI -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
