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.
Steps to reproduce the error: 1. Create a new project "Maven > Web Application" 2. Create a new servlet "MavenPrjServlet" 3. Invoke "profile file" on servlet. A browser window is opening, but the profiler is unable to connect to the target VM - even after waiting for approx. 5min. Netbeans version information ---------------------------- Product Version: NetBeans IDE 8.0 Beta (Build 201401091443) Java: 1.8.0-ea; Java HotSpot(TM) 64-Bit Server VM 25.0-b63 Runtime: Java(TM) SE Runtime Environment 1.8.0-ea-b121 System: Linux version 3.11.0-12-generic running on amd64; UTF-8; en_US (nb) User directory: /home/smohr/.netbeans/8.0beta Cache directory: /home/smohr/.cache/netbeans/8.0beta Operating System : Linux Mint 16 Linux positron 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Created attachment 143892 [details] IDE log. For me it seems that maven application is not deployed but profiler is connected successfully. My steps: - create maven web project (GlassFish, Java EE 7) - create new servlet - right-click servlet and choose "Profile File" - choose CPU, Advanced and click Run - server is started, profiler connected but application is not deployed and subsequently browser is not opened (see messages.log) Product Version: NetBeans IDE 8.0 Beta (Build 201401091443) Java: 1.8.0-ea; Java HotSpot(TM) 64-Bit Server VM 25.0-b65 Runtime: Java(TM) SE Runtime Environment 1.8.0-ea-b123 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
I experienced the same problem on windows 8, while trying to profile a small maven project. Netbeans version information: OS: Windows 8 (6.2) Product Version: NetBeans IDE 8.0 (Build 201403101706) Java: 1.7.0_51; Java HotSpot(TM) Client VM 24.51-b03 Runtime: Java(TM) SE Runtime Environment 1.7.0_51-b13 System: Windows 8 version 6.2 running on x86; Cp1252; en_US (nb)
*** This bug has been marked as a duplicate of bug 267458 ***