It is a log of steps that I had to do get JBoss Profiler running to analyze a running instance of JBossAS on Windows with JDK 1.4.
The files you need for run time analysis is:
jvmpi\windows\jbossInspector.dll (For linux, it's jvmpi/linux/libjbossInspector.so)
Modify path variable to include directory containing jbossInspector.dll
Verify that DLL is in path by running java -XrunjbossInspector:/tmp Foo. If the only error message you get is Class Foo not found, your native library installation is working. For linux, do export LD_LIBRARY_PATH=PATH_TO_SO(e.g. export LD_LIBRARY_PATH=/home/pjha/profiler/jvmpi/linux)
Deploy jboss-profiler-noAOP.sar and jboss-profiler.war to jbossas which you want to profile.
Modify run.bat as follow:
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XrunjbossInspector:
Go to http://localhost:8080/jboss-profiler to see profiler console. Click Run Time Profiler
Enter the directory you chose when you modified run.bat
Profiler should have picked the process id for the runnng JBoss.
Once you hit submit, you probably will not see any log etc because you have not yet asked profiler to start profiling.
Now, hit mbean=Native-profiler on jmx-console page of jboss.
Invoke acitvate method of mbean. Profile wills start tracking jvm calls
Run your test which may include seeing particular page, invoking a webservice client, sending a message to JMS.
Once you are done with your work, hit stop action of profiler mbean.
Now, Repeat the step starting from http://localhost:8080/jboss-profiler and you should see list of method calls with detail information.