Possibilities
- The Profiler settings are excluding your classes. Change the excludes in the Profiler settings.
- Your application was idle while the profiler was running. Attach the profiler then cause the program to execute the code you want to profile.
- You might be profiling the wrong JVM. RMI makes it pretty easy to call into another JVM. Maybe you need to be profiling the other side of that RMI connection.
There is a "Settings" checkbox on the Profiler tab. If you check the Settings box another panel will show up that lets you configure what classes the profiler collects data about.
Here is a screenshot.