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.

Bug 160137 - Glassfish server not working when run from NetBeans (Works manually though!)
Summary: Glassfish server not working when run from NetBeans (Works manually though!)
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All Windows Vista
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-11 22:03 UTC by gravitech
Modified: 2009-11-16 10:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gravitech 2009-03-11 22:03:18 UTC
I used to run Netbeans and glassfish as my application server, however, yesterday glassfish suddenly stopped starting up
when i tried to run a web application. For the life of me i cannot figure out why. After mucking around with it for a
few hours i'd had enough and decided that i was just going to uninstall netbeans and glassfish, download netbeans 6.5
(glassfish and tomcat included) and reinstall it.

So i did, i reinstalled netbeans IDE 6.5, J2SE, J2EE, J2ME, Glassfish V2 UR2, Glassfish V3 and Tomcat.

I booted up netbeans, installed all the updates as recommended, and then tried to start glassfish V2. It gave me the
same error as before and told me to look at the server logs ...


[code]11/03/2009 11:32:06 PM com.sun.enterprise.admin.servermgmt.launch.ASLauncher buildCommand

INFO: 
C:/Program Files/Java/jdk1.6.0_10\bin\java
-Dcom.sun.aas.instanceRoot=C:/glassfish-v2ur2/domains/domain1
-Dcom.sun.aas.ClassPathPrefix=
-Dcom.sun.aas.ClassPathSuffix=
-Dcom.sun.aas.ServerClassPath=
-Dcom.sun.aas.classloader.appserverChainJars.ee=
-Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,j2ee-svc.jar
-Dcom.sun.aas.classloader.excludesList=admin-cli.jar,appserv-upgrade.jar,sun-appserv-ant.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
-Dcom.sun.aas.classloader.optionalOverrideableChain=webservices-rt.jar,webservices-tools.jar
-Dcom.sun.aas.classloader.serverClassPath.ee=/lib/hadbjdbc4.jar,C:/glassfish-v2ur2/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,/lib/dbstate.jar,/lib/hadbm.jar,/lib/hadbmgt.jar,C:/glassfish-v2ur2/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.classloader.serverClassPath=C:/glassfish-v2ur2/lib/install/applications/jmsra/imqjmsra.jar,C:/glassfish-v2ur2/imq/lib/jaxm-api.jar,C:/glassfish-v2ur2/imq/lib/fscontext.jar,C:/glassfish-v2ur2/imq/lib/imqbroker.jar,C:/glassfish-v2ur2/imq/lib/imqjmx.jar,C:/glassfish-v2ur2/lib/ant/lib/ant.jar,C:/glassfish-v2ur2/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
-Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,jesmf-plugin.jar,/lib/dbstate.jar,/lib/hadbjdbc4.jar,jgroups-all.jar,C:/glassfish-v2ur2/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Program
Files/Java/jdk1.6.0_10/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,com-sun-commons-launcher.jar,com-sun-commons-logging.jar,C:/glassfish-v2ur2/imq/lib/jaxm-api.jar,C:/glassfish-v2ur2/imq/lib/fscontext.jar,C:/glassfish-v2ur2/imq/lib/imqbroker.jar,C:/glassfish-v2ur2/imq/lib/imqjmx.jar,C:/glassfish-v2ur2/imq/lib/imqxm.jar,webservices-rt.jar,webservices-tools.jar,mail.jar,appserv-jstl.jar,jmxremote_optional.jar,C:/glassfish-v2ur2/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar,C:/glassfish-v2ur2/updatecenter/lib/updatecenter.jar,C:/glassfish-v2ur2/jbi/lib/jbi.jar,C:/glassfish-v2ur2/imq/lib/imqjmx.jar,C:/glassfish-v2ur2/lib/ant/lib/ant.jar,dbschema.jar
-Dcom.sun.aas.configName=server-config
-Dcom.sun.aas.configRoot=C:/glassfish-v2ur2/config
-Dcom.sun.aas.defaultLogFile=C:/glassfish-v2ur2/domains/domain1/logs/server.log
-Dcom.sun.aas.domainName=domain1
-Dcom.sun.aas.installRoot=C:/glassfish-v2ur2
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.promptForIdentity=true
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.help,javax.portlet
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.updatecenter.home=C:/glassfish-v2ur2/updatecenter
-Ddomain.name=domain1
-Djava.endorsed.dirs=C:/glassfish-v2ur2/lib/endorsed
-Djava.ext.dirs=C:/Program Files/Java/jdk1.6.0_10/lib/ext;C:/Program
Files/Java/jdk1.6.0_10/jre/lib/ext;C:/glassfish-v2ur2/domains/domain1/lib/ext;C:/glassfish-v2ur2/javadb/lib
-Djava.library.path=C:\glassfish-v2ur2\lib;C:\glassfish-v2ur2\lib;C:\glassfish-v2ur2\bin;C:\glassfish-v2ur2\lib
-Djava.security.auth.login.config=C:/glassfish-v2ur2/domains/domain1/config/login.conf
-Djava.security.policy=C:/glassfish-v2ur2/domains/domain1/config/server.policy
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Djavax.net.ssl.keyStore=C:/glassfish-v2ur2/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/glassfish-v2ur2/domains/domain1/config/cacerts.jks
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djmx.invoke.getters=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000
-client
-XX:+UnlockDiagnosticVMOptions
-XX:MaxPermSize=192m
-Xmx512m
-XX:NewRatio=2
-XX:+LogVMOutput
-XX:LogFile=C:/glassfish-v2ur2/domains/domain1/logs/jvm.log
-cp
C:/glassfish-v2ur2/lib/jhall.jar;C:\glassfish-v2ur2\lib\appserv-launch.jar
com.sun.enterprise.server.PELaunch
start

[#|2009-03-11T23:32:12.852+0900|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting
Sun Java System Application Server 9.1_02 (build b04-fcs) ...|#]

[#|2009-03-11T23:32:12.977+0900|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=11;_ThreadName=pool-1-thread-2;com.sun.enterprise.interceptor.DynamicInterceptor;|MBeanServer
started: com.sun.enterprise.interceptor.DynamicInterceptor|#]

[#|2009-03-11T23:32:14.849+0900|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5098:
AS Socket Service Initialization has been completed.|#]

[#|2009-03-11T23:32:14.927+0900|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java
HotSpot(TM) Client VM;1.6.0_10;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.6.0_10]
from [Sun Microsystems Inc.]|#]

[#|2009-03-11T23:32:15.146+0900|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;|SEC1002:
Security Manager is OFF.|#]

[#|2009-03-11T23:32:17.345+0900|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=10;_ThreadName=main;|C:/glassfish-v2ur2/domains/domain1/config/.__com_sun_appserv_pid|#]

[#|2009-03-11T23:32:17.798+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:SunoneInterceptor
is now enabled|#]

[#|2009-03-11T23:32:18.734+0900|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143:
Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]

[#|2009-03-11T23:32:20.262+0900|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;server;|WEB0114:
SSO is disabled in virtual server [server]|#]

[#|2009-03-11T23:32:20.356+0900|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;__asadmin;|WEB0114:
SSO is disabled in virtual server [__asadmin]|#]

[#|2009-03-11T23:32:22.150+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079:
Initialization of AMX MBeans started|#]

[#|2009-03-11T23:32:23.180+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=12;_ThreadName=Thread-16;service:jmx:rmi:///jndi/rmi://osian-laptop:8686/jmxrmi;|ADM1504:
Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://osian-laptop:8686/jmxrmi].
 This is where the remote administrative clients should connect using the standard JMX connectors|#]

[#|2009-03-11T23:32:23.180+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=12;_ThreadName=Thread-16;true;|ADM1506:
Status of Standard JMX Connector: Active = [true]|#]

[#|2009-03-11T23:32:23.211+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|autoDeployment
status dir missing, creating a new one|#]

[#|2009-03-11T23:32:23.398+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy]
Selecting file C:\glassfish-v2ur2\lib\install\applications\MEjbApp.ear for autodeployment.|#]

[#|2009-03-11T23:32:25.988+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|deployed
with moduleid = MEjbApp|#]

[#|2009-03-11T23:32:26.175+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy]
Successfully autodeployed : C:\glassfish-v2ur2\lib\install\applications\MEjbApp.ear.|#]

[#|2009-03-11T23:32:26.175+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy]
Selecting file C:\glassfish-v2ur2\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]

[#|2009-03-11T23:32:32.228+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|deployed
with moduleid = __ejb_container_timer_app|#]

[#|2009-03-11T23:32:32.306+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy]
Successfully autodeployed : C:\glassfish-v2ur2\lib\install\applications\__ejb_container_timer_app.ear.|#]

[#|2009-03-11T23:32:32.306+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy]
Selecting file C:\glassfish-v2ur2\lib\install\applications\__JWSappclients.ear for autodeployment.|#]

[#|2009-03-11T23:32:32.836+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|deployed
with moduleid = __JWSappclients|#]

[#|2009-03-11T23:32:32.883+0900|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;|[AutoDeploy]
Successfully autodeployed : C:\glassfish-v2ur2\lib\install\applications\__JWSappclients.ear.|#]

[#|2009-03-11T23:32:33.569+0900|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;|WEB0302:
Starting Sun-Java-System/Application-Server.|#]

[#|2009-03-11T23:32:34.692+0900|INFO|sun-appserver9.1|com.sun.jbi.framework|_ThreadID=11;_ThreadName=pool-1-thread-2;|JBIFW0010:
JBI framework ready to accept requests.|#]

[#|2009-03-11T23:32:35.488+0900|WARNING|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;_RequestID=db2dfade-493c-4aad-a69e-6c63a251f106;|No
Principals mapped to Role [noaccess].|#]

[#|2009-03-11T23:32:36.128+0900|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;8080;|WEB0712:
Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080|#]

[#|2009-03-11T23:32:36.237+0900|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;8181;|WEB0712:
Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181|#]

[#|2009-03-11T23:32:36.252+0900|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;4848;|WEB0712:
Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848|#]

[#|2009-03-11T23:32:39.778+0900|INFO|sun-appserver9.1|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|SMGT0007:
Self Management Rules service is enabled|#]

[#|2009-03-11T23:32:39.918+0900|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application
server startup complete.|#][/code]


I dont know what most of that means, but if someone can see an error then please let me know.

When i try to use Tomcat, it works perfectly and the servlet/JSP deploy and run as they should.

Glassfish installation directory = C:\glassfish-v2ur2
PATH Environment variable = C:\apache-ant-1.7.1\bin;C:\Program
Files\Java\jdk1.6.0_10\bin;C:\glassfish-v2ur2\bin;C:\javaTests;C:\instantclient_11_1

My Operation system is Windows Vista Home Basic.



PLEASE NOTE:

When i try to start the Glassfish MANUALLY it works fine.

e.g (from a command prompt)

[code]asadmin start-domain domain1[/code]

Then i go to http://127.0.0.1:4848/ 

and it'll load up the log in page from which i can actually log into Glassfish.


Really hope someone can point out what I'm doing wrong with NetBeans

Thanks


Summary:

IDE = Netbeans 6.5
Server = Glassfish V2 UR2  (note, same thing happens with V3)
OS = Windows Vista Home basic edition
Comment 1 gravitech 2009-03-11 22:11:07 UTC
JRE = 1.6
Comment 2 Vince Kraemer 2009-11-16 10:34:06 UTC
Hi.  It looks like this got filed in a category that is not actively monitored, so it took way too long to end up in my queue.

Before I dig into this, is this still a problem for you?

Have you found a solution (and can start GF successfully from the command-line) or moved on (switch to Tomcat)?

There is a common problem for the IDE, which can strike without a lot of warning. It is related to port monitoring by firewall and virus detectors.

The IDE does a ping on the admin port, to try to detect whether the server actually started and is the server that we expect (since multiple servers can be started that might all sit on a port).

Some virus detectors start to listen to all ports and divert attacks (even when they are valid queries on ports that have not been listed as 'safe').

This thread has more info: http://forums.java.net/jive/message.jspa?messageID=263092

I am going to resolve this issue as incomplete, in part because it may not be worth pursuing so long after the initial report.  If you do want to pursue it, just reopen it and we can restart the analysis process.