Problem getting the profiler working

[Dennis Weyland]

Hello!

I have a problem getting the profiler working. I hangs during the
calibration process at "connection to the target vm". I tried out three
different (of the currently with my packet manager available) VMs
(java-6-sun-1.6.0.06, java-6-openjdk, java-1.5.0-sun-1.5.0.15). I am
using Netbeans 6.0.1 on Ubuntu.

Thank you for your help.

Best regards,
Dennis


---------------------------------------------------------------------
To unsubscribe, e-mail: address-removed
For additional commands, e-mail: address-removed

[Jiri Sedlacek]

Hi Dennis,

make sure that there's no firewall blocking profiler ports (by default the profiler uses 5140 &
5141, maybe try to turn off the firewall during calibration just to be sure) and that no exceptions
are logged in console / IDE logfile.

If you won't be able to resolve the problem, please file a bug report at
http://www.netbeans.org/issues/enter_bug.cgi?component=profiler and provide as much information as
possible (at least the IDE logfile).

Jiri


Dennis Weyland wrote:

[Dennis Weyland]

Hi Jiri,

is it possible to run the calibration process from command line or
something like that? Inside the IDE I do not get any error messages...

Dennis




Jiri Sedlacek wrote:

[Dennis Weyland]

I tried that again and got this error message:

init:
profile-init:
deps-jar:
Compiling 1 source file to
/home/weyland/NetBeansProjects/localsearch/build/classes
compile:
profile:
*** Profiler message (Tue Sep 16 14:50:38 CEST 2008): Starting target
application...
/usr/lib/jvm/java-6-sun-1.6.0.06/bin/java
-agentpath:/home/weyland/.netbeans/6.0/lib/deployed/jdk16/linux/libprofilerinterface.so
-Xbootclasspath/a:/home/weyland/.netbeans/6.0/lib/jfluid-server.jar:/home/weyland/.netbeans/6.0/lib/jfluid-server-15.jar
org.netbeans.lib.profiler.server.ProfilerServer
/home/weyland/.netbeans/6.0/lib/deployed/jdk16/linux 5141 10
____Profiler+Calibration+Run____
*** Profiler warning (Tue Sep 16 14:53:09 CEST 2008): timed out while
trying to connect to the target JVM.
*** Profiler error (Tue Sep 16 14:53:09 CEST 2008): connection with
server not open
/home/weyland/NetBeansProjects/localsearch/nbproject/profiler-build-impl.xml:71:
Calibration failed.
Please check your setup and run the calibration again.
BUILD FAILED (total time: 2 minutes 50 seconds)

Perhaps this can help in figuring out the exact problem...

Dennis



Jiri Sedlacek wrote:

[Jiri Sedlacek]

OK so try to invoke the calibration from terminal:

/usr/lib/jvm/java-6-sun-1.6.0.06/bin/java
-agentpath:/home/weyland/.netbeans/6.0/lib/deployed/jdk16/linux/libprofilerinterface.so
-Xbootclasspath/a:/home/weyland/.netbeans/6.0/lib/jfluid-server.jar:/home/weyland/.netbeans/6.0/lib/jfluid-server-15.jar
org.netbeans.lib.profiler.server.ProfilerServer /home/weyland/.netbeans/6.0/lib/deployed/jdk16/linux
5141 10 ____Profiler+Calibration+Run____


Have you disabled the firewall before the calibration??

Jiri


Dennis Weyland wrote:

[Dennis Weyland]

Hi Jiri,

thanks for your reply. Command line told me, that
libprofilerinterface.so cannot be found. Now I figured out, that my home
is mounted through the network here and I copied libprofilerinterface.so
to another (not network mounted) place. In this case I could start the
process and got this output:

Profiler Agent: Initializing...
Profiler Agent: No options
Profiler Agent: Initialized succesfully
Profiler Agent: Waiting for connection on port 5141 (Protocol
version: 8)

Is this the correct behaviour? In that case I try to fix the network
mount....

Dennis

---------------------------------------------------------------------
To unsubscribe, e-mail: address-removed
For additional commands, e-mail: address-removed

[Jiri Sedlacek]

Yes, this is the expected behaviour. However, the fact that you had to copy the .so library manually
to be able to access it points to the problem - the profiler is unable to use the .so library (and
probably other files) on the network and that's why the calibration fails.

You should either fix access to the network files (access rights?) or use a local user directory for
profiling (probably more reliable).

Jiri


Dennis Weyland wrote: