Please consider adding a "Quick Start" guide to the JBoss Profiler documentation to help new users get up and running quickly. Here's my first draft based on JBoss Profiler 1.0.CR4 with JBoss App Server 4.0.5 and Java 1.5: Installation: 1) copy jboss-profiler-noAOP.sar to the JBoss AS deploy directory 2) put jbossInspector.dll in your PATH (Windows) or libjbossInspector.so in your LD_LIBRARY_PATH (Linux/Unix) 3) copy jboss-profiler.war to the JBoss AS deploy directory Configuration: 1) Add something like this to the JBoss JVM options: -XrunjbossInspector:/tmp/profiler,include=com.unisys,ignore=*,memory=false Make sure the output directory (/tmp/profiler in this example) exists. Usage: 1) In the jmx-console, use the jboss.profiler Native-profiler mbean to activate profiling 2) Exercise your application 3) In the jmx-console, use the jboss.profiler Native-profiler mbean to stop profiling (if you forget to do this, you will probably get a java.io.EOFException when you try to use the analyzer war) 4) Analyze results using the JBoss Profiler web app at localhost:8080/jboss-profiler Example analysis: a. Click on 'Runtime Profiler' b. Enter the output directory, for example, /tmp/profiler c. Check 'Stack on methods', uncheck other options and submit d. Click 'click here' e. Click the 'All Methods' link to get a view of time allocation among individual methods Regards, Scott Dawson Unisys View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057532#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...