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

Summary: improving profiler troubleshooting doc for remote profiling
Product: profiler Reporter: ddv36a78 <ddv36a78>
Component: BaseAssignee: issues@profiler <issues>
Status: NEW ---    
Severity: blocker    
Priority: P3    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:

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.