RE: WAS 2.0 thread CPU hog

["Larry Loen" <lwloen@xxxxxxxxxx>]

>Larry

>What can I do to determine exactly what it is doing?

>Using WRKJOB command, here is the program
>stack during a RUN status in
>descending order on the thread in question:
[delete details]

Keep going deeper into the stack.

However, it isn't likely to be garbage collection; this looks like
some periodic task in the servlet processing somewhere.

Notice the revealing name --

com-ibm-servlet-engine-SEServletManager-validateServlets()V
com-ibm-servlet-engine-SEServletManager$ServletValidator-handleAlarm(Lcom-su

n-server-util-Alarm;)V
com-sun-server-util-AlarmManager-run()V
java-lang-Thread-run()V

Demangle these and you get something like:

package com.ibm.servelet.engine;

class SEServeletManager  {

    void validateServlets();
    class ServletValidator {
     void handleAlarm(com.sun.server.util.Alarm);
    }
}

Note the use of an "inner class"

and, probably,

package com.sun.server.util;

class AlarmManger extends Thread {
   void run() { super.run(); }  // ?? maybe implements Runnable
}

I'd investigate the Javadoc for these things if they are available.

If they aren't public methods, though, you may have to settle for the
more generic description of the servlet engine process.  I don't know,
offhand, exactly what these are.

Larry W. Loen  -   Senior Java and AS/400 Performance Analyst
                          Dept HP4, Rochester MN


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---