JBoss-profiler-2.0.Beta4 or 5 with jboss-5.1.0.GA-jdk6

[h2kinfosys]

I installed jboss-5.1.0.GA-jdk6\jboss-5.1.0.GA and also
Downloaded JBoss-profiler-2.0.Beta4 and also JBoss-profiler-2.0.Beta5
=====
Followed the instructions to copy the jar files and properties files
First I tried with JBoss-profiler-2.0.Beta5 and tried to start the jboss profiler by executing the following command.
-----------
C:\jboss-profiler-2.0.Beta4\>java -Xmx512m -Djboss-profiler-client.properties=jboss-profiler-client.properties -jar jboss-profiler-client.jar startProfiler
-----------
I executed this command on Windows XP , command prompt.
After executing this command, simply back to the commpand prompt.
no output.
when I tried with out any options at the end, it is displaying all the options like startProfile, stop etc..

=========
I opened jmx console (http://localhost:8080/jmx-console/) and at the end I saw org.jboss.profiler at the end of the list under Object Name Filter.
===========
When I tried to open http://localhost:8080/jboss-profiler/

just blanck page with small icon( some thing like I ) on left hand top of the screen.
==============
Please let me know how we can display the JBoss-Profiler from IE browser or Mozilla?
==============

Also Want to know if we can find out live connection pools from web console or jmx console or JBoss profiler?
========
Quesion 1 : When I executed startProfiler from command prompt, nothing is happend, just back to the command prompt.

Question 2: When I open the browser with http://localhost:8080/jboss-profiler/ : just empty page with a very small icon on top left corner of the page : how to display the values from JBOss profiler ?

Thank you,
Narasimha

[kiran_yalamati]

Hi Narasimha,

                     to get the report first start the server then use -jar jboss-profiler-client.jar startProfiler command .then open run your application or test case then use the -jar jboss-profiler-client.jar stopprofiler command. finally use the java -jar jboss-profiler-client.jar snapshot command to get the report.

[theoden]

As said just above the behaviour you observed is the standard behaviour the start command line lunch the profiler, you run your tests cases ans then stop the profiler to gain access to the report.

Seem's that all is working correctly .