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.
I noticed several times that when I add a app server to IDE (any glassfish build) and start it, then create a web app and run the web app the server is first stopped and then started again. I think I would start the server first if I wanted to do a demo, then I would develope an application - so that I do not have to wait for it to start. It would be really anoying if it was restarted - I consider this a show stopper. Steps to reproduce: 1. clean IDE build 2. download and install glassfish (run setup.xml) 3. add gf in server manager 4. start gf from server registry 5. create a web app (I added jsf, created entity from db, generated jsf from entity) 6. Run the web app. The server will be stopped, started, then the app deploys OK
I can't reproduce the issue in latest NB build 20060308 and Glassfish build 39. Pavle, can you still reproduce the issue with latest build? Thanks
It happens to me _only_ if glassfish (new domain) has not been started yet (= is started for the first time). Step 2 from Pavel's steps is very important for reproducing this. That means that if you: -install glassfish and run setup.xml -start glassfish -stop glassfish -start glassfish again then the issue does not occur
it's because we do change the debug option on the instance See the domain diff: < <java-config classpath-suffix="" debug-enabled="false" debug-options="-X debug -Xrunjdwp:transport=dt_shmem,server=y,suspend=n,address=localhost4848" env -classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g" system-classpath="$ {com.sun.aas.installRoot}/lib/appserv-launch.jar"> --- > <java-config classpath-suffix="" debug-enabled="false" debug-options="-X debug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009" env-classpa th-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-op tions="-iiop -poa -alwaysgenerate -keepgenerated -g" system-classpath="${com.sun .aas.installRoot}/lib/appserv-launch.jar"> This triggers the flag to restart. Maybe we should try again to use dt-socket and see if NetBeans IDE is better now. This change was there because we had issues to restart the server or re-attach to a debugged session once the session what stopped. It was back in the 4.1 days, so we need to see if it is better now. Otherwise, we could ignore the reset flag when we do this change at init time, because in anycase, a debug session would trigger a server restart... This might be the simplest solution for now.
Server's 'debug-options' is set when the start command is called via the IDE. This results in server going into restart mode and hence the subsequent deploy results in a restart before the deploy. Moved the 'debug-options' to stop command which will resolve this issue and will also ensure that the correct debug-options are set. In addition, we might want to revisit the requirement for setting the 'debug-options' as per Ludo's comments above.