2006/4/19, David Delbecq <[EMAIL PROTECTED]>: > > Hi,
Hey! "or other processes may end up using 100% CPU as well and presenting the > same behavior while on strace" If you mean also non java processes have similar problems, randomly, i > bet you may have either an OS issue (which affect all processes > randomly) either an hardware issue (corrupting RAM segments?) No, java processes only. And tomcat is the only java-using application running on these servers. If you want to discover where you tomcat is eating all it's CPU cycle, i > recommend you issue a 'kill -3 <java process id>', this will dump in > java stdout a list of current stacktrace, including native frames. You > might get there hints on what is problematic (might simply be an > HttpThread in a webapp endless loop) Any hints on how to associate a thread with an OS PID? Or any other way of identifying what thread is the culprit? I have played with the kill -3 feature, but didn't get very far investigating the output. =( Thanks! -- Gustavo Noronha Silva Coordenação de Segurança e Sustentação Ministério do Desenvolvimento Social - Brasil
