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.
Build: NetBeans IDE Dev (Build 200902261558) VM: Java HotSpot(TM) Client VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b02 OS: Windows XP, 5.1, x86 User Comments: GUEST: Activating GlassFish v1,v2 in the Plugins davisn: 1. Install NB Trunk All version build, dated 02/19/2009 2. Launch the IDE 2. Select to activate GlassFish V2 server pluign While the activation is happing, select to activate GlassFish V3 Prelude server GUEST: activating Web applications chrislundin: activating plugin "Glassfish v3 Prelude" pribyl: I installed latest build ("Java", with J2EE support and server installation) and started with clean userdir. When I selected New Project - Java Web - Web Application, I was prompted to activate the appropriate module. After hitting "Activate" button, this NPE was thrown. Note: I had some issues with Glasfish v3 before, so I uninstall it with the IDE and tried to reinstall it. Obviously, there is still something wrong with that. Stacktrace: org.netbeans.modules.j2ee.deployment.plugins.api.InstanceCreationException: Failed to create instance GlassFish v3 Prelude Domain. See the server log file for details. at org.netbeans.modules.j2ee.deployment.impl.ServerRegistry.addInstance(ServerRegistry.java:356) at org.netbeans.modules.j2ee.deployment.plugins.api.InstanceProperties.createInstancePropertiesWithoutUI(InstanceProperties.java:260) at org.netbeans.modules.glassfish.javaee.JavaEEServerModuleFactory.createModule(JavaEEServerModuleFactory.java:112) at org.netbeans.modules.glassfish.common.GlassfishInstance.updateModuleSupport(GlassfishInstance.java:157) at org.netbeans.modules.glassfish.common.GlassfishInstance.<init>(GlassfishInstance.java:125) at org.netbeans.modules.glassfish.common.GlassfishInstance.create(GlassfishInstance.java:196)
Created attachment 77448 [details] stacktrace
Created attachment 77449 [details] Server logs and messages.log
this looks like a v3 plugin issue.
putting all the case under on issue... *** This issue has been marked as a duplicate of 156351 ***
v.