analyzer displays empty result, even with log files created.

[michele.curioni]

Hi there,
I'm running JBoss 4.02 on Windows XP.

I managed to run the profiler, and I think it collected some data, because the directory is full of logs, and one of them is quite big.

When I run the web app to analyze the results, it seems to be running ok, but it doesn't produce any result.

I get the following output after specifying the directory where the logs are:

Opening ..\serverspy_2424_thread_1158854346999_12468750000_15.log.gz
Opening ..\serverspy_2424_thread_1158854358761_1390625000_16.log.gz etc.
....
Processed 10000 registers (21%)
Processed 20000 registers (42%)
Processed 30000 registers (61%)
Processed 40000 registers (82%)
Process Finished.... click here

After this the following pages only display tables, with no content.

Any idea?

Thanks,
Michele

[clebert.suconic]

I guess you're filtering too much.


Try using (-XrunjbossInspector:/YourLogDir) Only

[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

[clebert.suconic]

Are you sure you started/stopped capturing it correctly?

[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

[michele.curioni]

Hi guys,
any idea on this?

Thanks,
Michele

[clebert.suconic]

You are doing something wrong...


Send me a private e-mail... I will try to help you

[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