>From recent experience with this kind of problems you may want to run "prstat >-L -p <PID>" on the process using the CPU to identify the thread that loops.
Then use gdb to either attach to the process, or to analyse a core that you have forced by sending the process an adequate signal (e.g. QUIT, TRAP or ABRT, for example kill -ABRT <PID>) In gdb "info threads" will list all the threads. You should be able to find the thread that is looping, change to the thread with "thread <thread id>" and with "bt full" dump a stack trace that will allow you to identify the function(s) involved in the loop. That should give you an idea of the faulty module. Lykke til -ascs -----Original Message----- From: Kjell Grindalen [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 23, 2005 3:43 PM To: users@httpd.apache.org Subject: SV: [EMAIL PROTECTED] High cpu load on apache Well, actually i like it :-) After going to preforked, instead of threaded, i ahve seen a pattern, that it consistently hangs on sa component called showpictureservlet component..wich is websphere.. I wanted to just og here first to see if i had done something very wrong along the way. Thank you! Mvh Kjell Grindalen --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
