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.
Product Version: NetBeans IDE 6.7 RC2 (Build 200906030001) Java: 1.6.0_14-ea; Java HotSpot(TM) Client VM 14.0-b12 System: Linux version 2.6.28-11-generic running on i386; UTF-8; en_US (nb) -download and unzip the order system project at http://wiki.netbeans.org/attach/ProfilerTestSpecification/order_system.zip -open it in the ide -start the glassfish(2.1) server in profile mode -invoke main menu|profile|attach profiler -Select Project OrderSystem. Click "change" link next to "Attach mode" label in the bottom to open Attach Wizard, select J2EE Web/App Server target type, server type glassfish, local attach method, direct attach invocation, press next and finish the wizard. -In the attach profiler dialog: select Monitor Application, enable Threads and confirm the Select Profiling Task dialog by Attach button. The web application should start. Detach the profiler and stop the application. The glassfish server shoul be still running. -invoke main menu|profile|attach profiler again. Select -Select Project OrderSystem. All the other settings should be already set, so there is no need to set them again. -Start the profiler session by clicking on 'attach' button. The profiler cannot connect to the server or the application - the 'progress' window hangs forever.
Created attachment 83157 [details] IDE log
Created attachment 83158 [details] glassfish log
Created attachment 83159 [details] messages.log
It happens with java 1.5.0_19 as well.
The second profiling session cannot be simply started by invoking the Attach again - the profiler is configured for direct attach. Either you kept the server running and you should use dynamic attach to profile it again or the server is already stopped and you should start it again for profiling. Closing as invalid, wrong workflow.