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 158230 - improving profiler troubleshooting doc for remote profiling
Summary: improving profiler troubleshooting doc for remote profiling
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-09 20:27 UTC by ddv36a78
Modified: 2009-02-09 20:27 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 ddv36a78 2009-02-09 20:27:10 UTC 
During the first steps of a remote profiling phase, NetBeans says "Connecting to the target VM".

I have lost few *hours* today, while not understanding why I could not connect to a target VM, and finally, I have
discovered NetBeans was going through the proxy to reach the target machine. I was not expecting NetBeans to go through
the proxy (to be clearer, I have forgotten the proxy effect). 

I suggest to add to "profiler troubleshooting doc" and/or "profiler FAQ" the fact, if one could not connect to a target
VM, it may be caused by the proxy configuration and the user is invited to check that configuration.