Thanks Clebert,
For the forum:
the problem was the options I used to start JBoss in profiler mode.
I used:
-XrunjbossInspector:C:\\performance\\profiler,start=org.ex.Main
the 'start' parameter tells the profiler to wait for a particular class in the
trace before collecting data. Given that the class I specified is not in my environment,
all the data collected was ignored.
I removed the option, and now it works fine.
Clebert also suggested to use the option memory=false to avoid cluttering the data with
memory stats, if you don't need them.
Cheers,
Michele
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974966#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...