-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sam,
On 2/24/2009 1:54 PM, Sam Hokin wrote: > Mark Thomas wrote: >> Sam Hokin wrote: >>> Thanks, Chris. I ran e2fsck with the -c option, which runs badblocks, >>> when I tested it earlier. And I just ran badblocks again - 0 bad blocks >>> found. I wish I could fix this by simply as swapping out a bad disk >>> (notwithstanding Andre's desire for intellectual pursuits), but I really >>> think it's software, either in some service mucking up the JVM or the >>> JVM itself. But it only manifests itself under Tomcat, and then only >>> when this particular package is imported. >> >> Do you see the same issue if you pre-compile that JSP? > > Surprisingly, yes. So it's not only a compilation issue. After some > individual tests, I compiled the JSPs from the four sites I have running > on this server and restarted Tomcat, and the LONG delay before Tomcat > begins serving page requests continues. ... and what is happening when you take a thread dump. Is it File.exists() taking forever again? If that's the case, the class loading is what's taking forever. I have no idea what could be causing that other than a disk read error (or network latency, but you mentioned you weren't using NFS or anything like that). Someone mentioned running strace which sounds like a good idea to me. You'll just have to sift through a ton of information to find what you're looking for since the JVM performs a /lot/ of system calls during its operation. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmkbIoACgkQ9CaO5/Lv0PAHFQCeKMwKXF3xU655W54unmGGeJx7 66wAn3hwEPghxTzMWv3Be7W4NIfQSr2o =53TD -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
