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.
-Unable to start GlassFish V3 server if the NB IDE is launch from ..\nb_all\web-main\nbbuild\netbeans\bin directory -This problem caused the glassfish.javaee qa-functional test failed on most the machines it run Steps To Reproduce: 1. hg check the web-main build -> build it 2. From the ..\nb_all\web-main\nbbuild\netbeans\bin start the Netbean IDE (eg, netbeans --userdir E:\sun\temp\netbean-test) 3. From Tools -> Plugin menu, select install the GlassFish V3 Enabler plugin 4. Restart the IDE -> select to enable JavaEE and Web components 5. Install GlassFish V3 promoted server (b56) 6. Register the b56 V3 server 7. Right-click at the b56-V3 server, select Properties menu -> click Java tab and add the jdk1.6.0 path -> close the dialog to save the change 8. Right-click on the server, select Start menu BUG: V3 Server failed to start Log files are attached
Created attachment 85384 [details] server.log
Created attachment 85385 [details] messages.log
step 3 is not necessary. this implies that you can skip step 4 also.. how did you perform step 5? did you import old settings? Did you give the path to the 'Java Executable' or did you give a path to the jdk install? Did a dialog open that said something like... 'GlassFish v3 server can not be started with /export/home/bin/java'
Steps 5: Just normally download the b56 bits from website and then install the server: http://download.java.net/glassfish/v3/promoted/
Where is the server installed? Does it start with asadmin start-domain?
GF V3 b56 & 55 build has regression on window platform that does not create domain1 after install the server https://glassfish.dev.java.net/issues/show_bug.cgi?id=8676 I will either reproduce it on MacOS or use the latest window build b57 to reproduce it.
I installed b57 build at E:\sun\glassfishv3-b57 directory and re-tested the problem. The problem still happened. The server started for a while then it stopped. Below is the message from the server output Welcome to Felix. ================= INFO: Started bundle org.glassfish.core.kernel [71] INFO: Started bundle org.glassfish.common.glassfish-mbeanserver [42] INFO: Started bundle org.glassfish.common.util [58] INFO: Started bundle com.sun.enterprise.config [57] INFO: Started bundle org.glassfish.admin.config-api [179] INFO: Hibernate Validator null INFO: Instantiated an instance of org.hibernate.validation.engine.resolver.JPATraversableResolver. INFO: No META-INF/validation.xml found. Using annotation based configuration only! INFO: Started bundle com.sun.grizzly.grizzly-config [134] INFO: Started bundle org.glassfish.branding [28] INFO: Started bundle org.glassfish.common.internal-api [12] INFO: OK, finally using a master passsword: changeit REMOVE -- debug statement .... INFO: Started bundle org.glassfish.ejb.ejb-container [120] INFO: com.sun.enterprise.naming.util.NamingActivator@1c0bee6 called INFO: Started bundle org.glassfish.common.glassfish-naming [205] INFO: Started bundle org.glassfish.transaction.jta [127] INFO: Started bundle org.glassfish.common.glassfish-api [87] INFO: Started bundle org.glassfish.registration.glassfish-registration [161] INFO: Started bundle org.glassfish.flashlight.framework [197] INFO: Listening on port 8080 INFO: Started JMXConnector, JMXService URL = service:jmx:rmi:///jndi/rmi://socialnet:8686/jmxrmi INFO: Starting Grizzly Framework 1.9.17-RC2 - Wed Jul 29 14:53:53 PDT 2009 INFO: Started bundle org.glassfish.deployment.autodeploy [9] INFO: Network listener http-listener-2 on port 8181 disabled per domain.xml INFO: Listening on port 4848 INFO: Starting Grizzly Framework 1.9.17-RC2 - Wed Jul 29 14:53:53 PDT 2009 INFO: Started bundle org.glassfish.orb.connector [74] INFO: Started bundle org.glassfish.transaction.jts [117] INFO: Started bundle org.glassfish.common.container-common [172] INFO: Started bundle org.glassfish.admin.rest-service [164] INFO: Started bundle org.glassfish.jms.core [113] INFO: Started bundle org.glassfish.admin.monitoring-core [6] INFO: Started bundle org.glassfish.deployment.common [68] INFO: GlassFish v3 startup time : Felix(3875ms) startup services(3313ms) total(7188ms) INFO: [Thread[GlassFish Kernel Main Thread,5,main]] started INFO: felix.fileinstall.poll (ms) 5000 INFO: felix.fileinstall.dir E:\sun\glassfishv3-b57\glassfish\domains\domain1\autodeploy-bundles INFO: felix.fileinstall.debug 1 INFO: felix.fileinstall.bundles.new.start true
I don't think it matters how NetBeans is started. I hit this bug when I started yesterday's nightly dev build from the Windows Start menu. Original message sent to tools-as alias: I'm using GlassFish v3 b57 (the latest promoted build), and have configured it with trunk build 200907281401. If I try to start GlassFish through the Server node of the Services pane, it won't start, and shows an error dialog. Similarly, if you start GlassFish on the command line and refresh the status in NetBeans, it isn't recognized as being started. My environment: Product Version: NetBeans IDE Dev (Build 200907281401) Java: 1.6.0_12; Java HotSpot(TM) Client VM 11.2-b01 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Documents and Settings\ian\.netbeans\dev GlassFish version: GlassFish v3 (build 57)
can replicate.
Integrated into 'main-golden', will be available in build *200907310201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/5104ea08efe1 User: vince kraemer <vkraemer@netbeans.org> Log: #169395: extra colon in install location value confused the parse for the hostname
in the build
*** Issue 169850 has been marked as a duplicate of this issue. ***