This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 136872 - Cannot connect to remote profiler
Summary: Cannot connect to remote profiler
Status: RESOLVED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-10 04:27 UTC by lava12345
Modified: 2009-09-18 13:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lava12345 2008-06-10 04:27:00 UTC
Netbeans 6.1 cannot connect to remote profiler in linux machine with latest remote profiler pack installed. It connects
first time and shows results. The filtered classes are also shown.
Next time if buffer is emptied or Profiling options are changed it does not work. Looking at blogs it looks that JVMTI
Invalid classes no. 21 bug is seen.
It is hampering daily tasks as i urgently need to produce a report to my Director.
Netbeans 6.1 is also in windows and both use jdk 1.6 latest version _003.
Comment 1 lava12345 2008-06-10 04:51:40 UTC
I run profile-16.sh in bin of remote profiler pack.
After I attach profiler, I get like this:
./profile-16.sh 
Profiler Agent: Initializing...
Profiler Agent: Options: >/root/bin/../lib/,5140<
Profiler Agent: Initialized succesfully
Profiler Agent: Waiting for connection on port 5140 (Protocol version: 8)
Profiler Agent: Established remote connection with the tool
Usage: java [-options] class [args...]
           (to execute a class)
   or  java [-options] -jar jarfile [args...]
           (to execute a jar file)

where options include:
    -d32          use a 32-bit data model if available

    -d64          use a 64-bit data model if available
    -client       to select the "client" VM
    -server       to select the "server" VM
    -hotspot      is a synonym for the "client" VM  [deprecated]
                  The default VM is server, 
                  because you are running on a server-class machine.

    -cp <class search path of directories and zip/jar files>
    -classpath <class search path of directories and zip/jar files>
                  A : separated list of directories, JAR archives,
                  and ZIP archives to search fo
Comment 2 Jiri Sedlacek 2008-06-10 10:38:46 UTC
You should use "profile-16.sh" script the same way as you use "java" command, for example to start an application from
myapp.jar you should invoke "./profile-16.sh -jar myapp.jar". In fact you've invoked just "java" which correctly
produces the "Usage: java [-options] class [args...] ..." output.
Comment 3 lava12345 2008-06-11 02:48:39 UTC
Thanks for the second portion answer. My original problem is:
I connect from machine 1 to machine 2 with remote profiler. Machine 1 in Linux with netbeans starts profiling machine 2
using Acttach mode.
It is successful. I can see invocations 1 in many beans in Live Results. Fine.
Now I log in a user. I do not want old invocations.
So I reset the buffer.
At this hour, the Profiler fails to connect to Machine 2.
Comment 4 Jiri Sedlacek 2008-06-11 09:21:57 UTC
I see. Could you please attach NetBeans logfile and logfiles/console outputs of profiled applications to this issue?
Comment 5 lava12345 2008-06-29 14:19:11 UTC
where is log files for remote profiler, please say i did not see any in remote machine or local for profiling logs.
Comment 6 J Bachorik 2008-08-28 10:54:28 UTC
Your local logs are in <nbuserdir>/var/log/messages.log
The remote logs are plainly printed into the console output of the profiled application so it depends on your
application whether they stay in the console window or you write them to a file.
Comment 7 matusdekanek 2009-09-18 13:07:45 UTC
The needed information has not been provided for a year - resolving invalid. There is almost nothing we can do (the log 
is quite important to us).
Once you reproduce the problem and get the log, please attach it and reopen. Thanks