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.
debugging pojo application which tcp/ip/http connects to gfv3 causes gfv3 Admin Console app to load. also -- attempting to debugger attach to gfv3 when gfv3 not run in debug mode or debugger attaching to gfv3 when is run in debug mode causes Admin Console app to load on gfv3 server. this info has been reported on grizzly, glassfish, netbeans mailing lists. i do not know which component has responsibility -- but how could gfv3 "know" that netbeans is running a program in debugger mode unless netbeans somehow "trigger" gfv3 to load the Admin Console app ??? normally Admin Console app is loaded when one connects to gfv3 at http://localhost:4848 -- so perhaps netbeans is doing this for some reason when running app which network connects to gfv3 when the app is run in debug mode ???
if after netbeans triggers gfv3 to load Admin Console app -- gfv3 is restarted by netbeans without restarting netbeans -- the Admin Console app is not triggered to be loaded by debugging the test app; if gfv3 is restarted by netbeans before the initial triggering of the loading of Admin Console -- it will be triggered to load upon next first debugging of the test app.
Unless there is some significant ill effect, this is just p4...
I did ./asadmin start-domain domain1 && tail -f /users/tomas/WS/gfr3122/glassfish/domains/domain1/logs/server.log to see what's happening during regular server startup now ... [#|2012-11-28T15:29:40.252+0100|INFO|glassfish3.1.2|javax.enterprise.system.tools.admin.org.glassfish.admin.rest.adapter|_ThreadID=20;_ThreadName=Thread-2;|REST00001: Listening to REST requests at context: /management/domain|#] [#|2012-11-28T15:29:40.361+0100|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.admin.adapter|_ThreadID=21;_ThreadName=Thread-2;|The Admin Console is already installed, but not yet loaded.|#] [#|2012-11-28T15:29:40.363+0100|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.admin.adapter|_ThreadID=21;_ThreadName=Thread-2;|The Admin Console is starting. Please wait.|#] [#|2012-11-28T15:29:41.463+0100|INFO|glassfish3.1.2|javax.enterprise.system.jmx.org.glassfish.admin.mbeanserver|_ThreadID=22;_ThreadName=Thread-2;|JMX005: JMXStartupService had Started JMXConnector on JMXService URL service:jmx:rmi://nb:8686/jndi/rmi://nb:8686/jmxrmi|#] [#|2012-11-28T15:29:43.732+0100|INFO|glassfish3.1.2|javax.enterprise.resource.webcontainer.jsf.config|_ThreadID=21;_ThreadName=Thread-2;|Initializing Mojarra 2.1.6 (SNAPSHOT 20111206) for context ''|#] [#|2012-11-28T15:29:45.694+0100|INFO|glassfish3.1.2|org.hibernate.validator.internal.util.Version|_ThreadID=21;_ThreadName=Thread-2;|HV000001: Hibernate Validator 4.3.0.Final|#] [#|2012-11-28T15:29:46.615+0100|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=21;_ThreadName=Thread-2;|WEB0671: Loading application [__admingui] at [/]|#] [#|2012-11-28T15:29:46.617+0100|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=21;_ThreadName=Thread-2;|CORE10010: Loading application __admingui done in 6,253 ms|#] [#|2012-11-28T15:29:46.617+0100|INFO|glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.admin.adapter|_ThreadID=21;_ThreadName=Thread-2;|The Admin Console application is loaded.|#] And it looks like the Admin Console application is being loaded by default now. ------------------------------------------------------------------------------- Also some server status checks like http://localhost:4848/__asadmin/__locations may cause the Admin Console application being loaded. I don't see any significant reason to change this behaviour. You may try NetBeans 7.3 build with GlassFish 3.1.2.2 from http://bits.netbeans.org/dev/nightly/latest/ to see what is the current behaviour. If you'll see some significant problem, feel free to file a new bug.