Hmm. I'm curious, what is the machine doing during those 4-30 seconds? Is it burning
CPU or I/O maybe? Is the JVM in RAM completely or are portions of it paged out to disk?
You could run "vmstat 2" in a terminal next to "tail -f acces.log". As
soon as you see the access log stall, check the vmstat to see what the box is doing, cpu
or disk.
Kees Jan
http://java-monitor.com/forum
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171811#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...