-
1. Re: analyzer displays empty result, even with log files crea
clebert.suconic Sep 21, 2006 12:25 PM (in response to michele.curioni)I guess you're filtering too much.
Try using (-XrunjbossInspector:/YourLogDir) Only -
2. Re: analyzer displays empty result, even with log files crea
michele.curioni Sep 21, 2006 12:43 PM (in response to michele.curioni)Thanks for the quick reply.
I tried changing the filters, and also the option that you suggested with no filter, but still no output.
When I ran with no filter, the web app took long time to process the results, but still didn't display anything.
Cheers,
Michele -
3. Re: analyzer displays empty result, even with log files crea
clebert.suconic Sep 21, 2006 12:46 PM (in response to michele.curioni)Are you sure you started/stopped capturing it correctly?
-
4. Re: analyzer displays empty result, even with log files crea
michele.curioni Sep 21, 2006 12:51 PM (in response to michele.curioni)Is there a way to tell?
I think so, otherwise there wouldn't be as many logs, and of such size.
I looked at JBoss log, and it says:
"Stopping DataGathering" after I called the stop method in the Profiler MBean.
Curiously, from web app I can save the results (which I cannot see), and the file saved is model.obj which takes 600k.
Cheers,
M -
5. Re: analyzer displays empty result, even with log files crea
michele.curioni Sep 27, 2006 9:24 AM (in response to michele.curioni)Hi guys,
any idea on this?
Thanks,
Michele -
6. Re: analyzer displays empty result, even with log files crea
clebert.suconic Sep 27, 2006 10:14 AM (in response to michele.curioni)You are doing something wrong...
Send me a private e-mail... I will try to help you -
7. Re: analyzer displays empty result, even with log files crea
michele.curioni Sep 28, 2006 1:04 PM (in response to michele.curioni)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