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 113034 - local calibration check for remote profiling
Summary: local calibration check for remote profiling
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-16 17:59 UTC by verhasi
Modified: 2007-08-31 14:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 verhasi 2007-08-16 17:59:54 UTC 
I tried to profile a remote server running on jdk15. The remote pack has been installed and the calibration was
successful. The local client neatbeans was running on jdk16. On the remote side i started the profile.sh and it was
waiting for the connection on port 5140. I started the profiler from neatbeans setting all the parameters and after
pressing the attach button it complained that the remote server has not been calibrated.
The reproduceable workaround was to calibrate a jdk15 locally on the client side. So I suppose that the profiler checks
the local calibration data existence instead of the remote. Please confirm that during profiling the remote calibration
is used.
bye
steve
Comment 1 Alexander Kouznetsov 2007-08-30 16:59:05 UTC 
I believe this is a P3 issue.
Comment 2 J Bachorik 2007-08-31 14:11:38 UTC 
tried to reproduce the problem on the trunk build but without success. the profiler correctly chooses the calibration
data to use depending on the profiling mode. 
because there is no such a problem with the current version i'm closing this issue as fixed