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 82180 - Unable to calibrate profile
Summary: Unable to calibrate profile
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All Linux
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-08 15:59 UTC by dhcavalcanti
Modified: 2013-10-16 07:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
log file (271.32 KB, text/plain)
2006-08-08 19:36 UTC, dhcavalcanti 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dhcavalcanti 2006-08-08 15:59:13 UTC 
I'm unable to calibrate the profile on Linux Fedora Core 5.

I get a popup box with the message: "Connecting to the target VM" and it stays
there.
Comment 1 ehucka 2006-08-08 16:17:45 UTC 
There can be many reasons for this behaviour. Could you attach your ide's log here? 
Profiler can be blocked by some 'strong' firewall too. Try to disable it for a
while and check calibration again.
Comment 2 dhcavalcanti 2006-08-08 19:34:21 UTC 
My firewall has been off.
I attached the log
Comment 3 dhcavalcanti 2006-08-08 19:36:09 UTC 
Created attachment 32663 [details]
log file
Comment 4 Tomas Hurka 2006-09-15 09:48:10 UTC 
To diagnose the problem, please run the following command (it is in your log file):
/usr/java/jdk1.5.0_07/bin/java -agentpath:/usr/netbeans-5.5beta2/profiler1/lib/deployed/jdk15/linux/
libprofilerinterface.so -Xbootclasspath/a:/usr/netbeans-5.5beta2/profiler1/lib/jfluid-server.jar:/usr/
netbeans-5.5beta2/profiler1/lib/jfluid-server-15.jar com.sun.tools.profiler.server.ProfilerServer /usr/
netbeans-5.5beta2/profiler1/lib/deployed/jdk15/linux 5141 10 ____Profiler+Calibration+Run____

from the shell and send us the output.
Thanks.
Comment 5 dhcavalcanti 2006-09-15 15:18:53 UTC 
I updated my JDK to version 1.5.0_08 and that resolved the issue.