I want to profile an application that is running under Eclipse.

I used the Attach Wizard in NetBeans and configured my VM arguments of my run
configuration in Eclipse according to the instructions provided by the Attach
Wizard.

I then choose Profiler | Attach Profiler from the menu. Analyze Performance.
Entire Application. Profile All Classes. I start the application in Eclipse. I
select Attach in NetBeans.

The profiler attaches and everything works fine. I see that
java.net.SocketOutputStream.socketWrite is using a lot of time. Detach.

Start Application in Eclipse. Profiler | Attach Profiler. Analyze Performance.
Entire Application. Exclude Java Core Classes. Attach.

The profiler attaches and everything works fine. I see that 8 of my methods are
using a lot of time. I add them to the instrumentation roots, selecting Preset:
Part of Application. Detach.

Profiler | Attach Profiler. Start application in Eclipse. Analyze Performance.
Part of application (8 methods). Customize Filter. Add an inclusive filter for
the Java Network Classes that includes java.net.

Attach. I add java.net.SocketOutputStream.socketWrite to the list of
instrumentation roots. Detach.

Profiler | Attach Profiler. Part of Application (9 methods, which now includes
the above-mentioned java.net method). Filter: Profile all Classes. Start
application in Eclipse. Attach.

After about a second the profiler stops without providing any results. The
application in Eclipse prints:

Profiler Engine: local connection with the tool

I click the stop button in Eclipse and after a few seconds it stops the
application. However, when I check the list of processes, the application is
still running.