|Problems when profiling a standalone tomcat [message #117150]
||Mon, 05 November 2007 12:35
Originally posted by: wjfang.gmail.com|
I partially succeed to profile a standalone tomcat by setting up the
following java option:
But two annoying problems exist:
1. I set up a filter including only my classes and excluding all others. But
many org.apache.*, java.* classes are still being profiled. And they are not
directly called from my classes.
2. Profiling data can only be captured when tomcat is attached from the very
beginning. If I start tomcat, run some client test code to warm it up, then
let eclipse tptp profiler to attach to the tomcat to capture profiling data,
no data is captured!
Is it because TPTP agent only instrument bytecodes when they are first
loaded? So when all classes are loaded, attaching profiler to tomcat has no
chance to instrument bytecode.
Any insight or suggestions? Many thanks in advance!