I took a quick look at the 3.2.8.SP1 release.
You'll need to get JBoss Remoting up and running on that release since it isn't
included. Otherwise you can't connect remotely.
You don't need to add anything to the classpath as the JARs reference each other from
inside the MANIFEST.MF files.
You modify the jboss-profiler.properties on the server where you need to profile. You then
use the client to connect to that server using the -h and -p arguments. The client is run
from the directory where you unpacked the distribution.
I think that it would be quicker to get the JBoss Profiler 1.0-CR4 release up and running
on your platform.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151447#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...