Looking as deep as possible with JBoss Profiler
I will show you now how you can use JBoss Profiler as your default choice for pre-production profiling tests.
Step 1 - Download the JBoss Profiler
Go to the JBoss Profiler Project page here, and download the CR4 Version from that page
Step 2 - For Linux Users
Copy to /usr/lib the file libjbossInspector.so from
Step 3 - Testing your Java Library Loading
You can test if Java is really loading our profiler Library, to do that execute the following command line in console:
[root@esilva jdk1.5.0_12]# java -XrunjbossInspector:/tmp Foo
Running process 9330
Exception in thread "main" java.lang.NoClassDefFoundError: Foo
If you see on the screen a result like that, you library is working fine.
Step 4 - Deploying a Spring Sample: countries.war for Profiling issues
After to build the sample using ANT, I copied the war file to my JBOSS_HOME/servers/default/deploy and that