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 57709 - Use a non-standard port for calibration
Summary: Use a non-standard port for calibration
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: iformanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-10 17:20 UTC by Jan Lahoda
Modified: 2007-02-12 22:07 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 Jan Lahoda 2005-04-10 17:20:07 UTC 
[recent profiler sources], JDK1.6.0b30, Windows, own build of NB (trunk, recent
sources).
Imagine the following situation: using NB profiler for the first time on a given
computer, and you run the profiled application in "attach on startup" mode
before starting the client NB. Then if the client NB tries to perform the
calibration, it cannot, because the (default 5140) port is used by a different VM.

If the calibration would use a different port, it would be possible to run the
calibration even in a case that was desribed above. Maybe even dynamically
assigned (the first free) port could be used for calibration?

I think this would improve the first time user experience.
Comment 1 mishadmitriev 2005-04-11 08:34:01 UTC 
Makes sense to me. Will try to implement this in M6.
Comment 2 mishadmitriev 2005-04-12 03:35:57 UTC 
Postponing until M7 - changes needed are not as trivial as expected, don't want
to introduce something in a rush just before M6 release.
Comment 3 iformanek 2005-06-19 12:35:32 UTC 
Fixed, calibration always uses "portNo + 1" port
Comment 4 ehucka 2006-10-09 12:10:07 UTC 
Verification of old issues.
Comment 5 Alexander Kouznetsov 2007-02-12 22:07:42 UTC 
Closing old issues.