I don't know if I wrote something wrong in the readme.txt, but the right way for doing that would be:
set JAVA_OPTS=-XrunjbossInspector:/temp/profiler,include=mypackage,ignore=* %JAVA_OPTS% Use ignore instead exclude ... Also... you can start the profiler just before you start your testcase. This way would be faster to capture what you need. The profiler statys sleeping and not capturing anything until you send the start signal. Another adivce is, to avoid compiling JSP (unless you use ignore=org.apache), because it generates lots of events. I have seen that same problem in other profilers if you don't use the right filter. If you want to, there is a new that is being generated in the build process. There is a MBean to start/stop the server. BTW: Have you navigated throught the graph of your methods? It's possible to detail what is inside a method! Clebert View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845334#3845334 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845334 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
