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.
NetBeans 201206080001 JDK 7u3 32-bit Glassfish I was running through the Maven test spec [1], and I am not able to profile a single file (as in test 3 [1]), or the project as a whole. I get the error below in the build output. Do note that I have several versions of Glassfish configured in the IDE, which could be contributing. [1] http://wiki.netbeans.org/TS_72_Maven#Test_suite:_Run.2C_Debug.2C_Profile.2C_Test_single_file Starting GlassFish Server 3+ GlassFish Server 3+ is running. In-place deployment at C:\Projects\Tests\osgi\WebAppPrj\target\WebAppPrj-1.0-SNAPSHOT Initializing... deploy?DEFAULT=C:\Projects\Tests\osgi\WebAppPrj\target\WebAppPrj-1.0-SNAPSHOT&name=org.test_WebAppPrj_war_1.0-SNAPSHOT&contextroot=/WebAppPrj&force=true failed. Instance is not GlassFish Server 3+. The module has not been deployed. See the server log for details. at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:210) at org.netbeans.modules.maven.j2ee.ExecutionChecker.performDeploy(ExecutionChecker.java:178) at org.netbeans.modules.maven.j2ee.ExecutionChecker.executionResult(ExecutionChecker.java:130) at org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:212) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153)
This is not a profiler problem - the important lines in the log are: failed. Instance is not GlassFish Server 3+. The module has not been deployed. check your project/app server settings, there is definitely something wrong there.
It does indeed seem like the server was not persisted correctly in the config file, and I was also not prompted to pick a server. This happens only the first time I try to profile the app, not having run it yet. Reassigning to the Glassfish server plugin, hoping that is more appropriate. :)
Steps to reproduce: 1. Create a Maven-based Web Application project. 2. Create a new servlet. 3. Right click on the project and choose Profile. The Progress... dialog stays there (I have not seen it complete). The execution of the profiling ends according to the output window, with the error as in the original description. This is all while having more than one version of Glassfish configured in the IDE. Running works fine, as does debugging. It is just with the profiling that I am experiencing this issue.
For me it doesn't work as well. My steps to reproduce: - install NetBeans and GlassFish from installer (daily build 7.3) - create web project - add new servlet - right-click project node and choose Profile - it shows progress dialog "Connecting to the target VM..." forever - if I cancel this dialog it prints Error occurred during initialization of VM Profiler Agent: -agentpath:<PATH>/profilerinterface should be called with two parameters: agent library failed to init: C:\Program Files\NetBeans Dev 201209020001\profiler\lib\deployed\jdk16\windows-amd64\profilerinterface.dll Profiler Agent: Initializing... Profiler Agent: Options: >C:\Program< Profiler Agent: path to Profiler agent libraries and port number, separated by comma, for example: Profiler Agent: java -agentpath:/mypath/profilerinterface=/home/me/nb-profiler-server/profiler-ea-libs,5140 Product Version: NetBeans IDE Dev (Build 201209020001) Java: 1.7.0_06; Java HotSpot(TM) 64-Bit Server VM 23.2-b09 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
Encountered this problem again during sanity testing of NetBeans IDE 7.3 Beta (Build 201209232010).
This is duplicate of P2 bug# 219370. It's the same stack trace and the same error message related to GlassFish startup issue. We are already working on it but we are facing some issues to reproduce it - it happens randomly, not with every deployment attempt. *** This bug has been marked as a duplicate of bug 219370 ***