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 20050209] I was wotking with App server and suddenly the server was restarted. See output window: init: deps-module-jar: deps-ear-jar: deps-jar: compile: compile-jsps: library-inclusion-in-archive: library-inclusion-in-manifest: Building jar: /home.local/blaha/testing/WebApplication2/dist/WebApplication2.war do-dist: dist: run-deploy: Stopping server Sun Java System Application Server 8 /home.local/blaha/SUNWappserver/bin/asadmin stop-domain domain1 Starting server Sun Java System Application Server 8 /home.local/blaha/SUNWappserver/bin/asadmin start-domain domain1 Distributing /home.local/blaha/testing/WebApplication2/dist/WebApplication2.war to [localhost:4848_server] deployment started : 0% Deployment of application WebApplication2 completed successfully Enable of WebApplication2in target server completed successfully All operations completed successfully run-display-browser: Browsing: http://localhost.czech.sun.com:8080/WebApplication2/ run: BUILD SUCCESSFUL (total time: 49 seconds)
This might be a feature, not a bug... Sometimes, if the server config is changed (new resources regsitered, class path changed, etc.. the server has a propery called restartNeeded (see the prop window of a running AS server to see its state. If the IDE detects this value to true, then j2eeserver module restarts the server. So what did you do before this restart?
I removed JMS resources. I understand, but user should be notified of server restart reason.
notification should be done at the j2eeserver level.
Setting the TM to 4.1.
This issue could happen in the following cases too. This also happens on WinXP, Solaris and JDS Linux Case 1 : If a web application contains any server resource (a data source). Every deployment of web module appserver is restarted. Even there is nothing is changed in application. Case 2 : If a web application contains Web services (which are getting compiled for each deployment and generating new classes). Appserver may think this are new classes in web module and restarts.
See also Appserver bug : 6312063
TM -> 5.0
*** Issue 72444 has been marked as a duplicate of this issue. ***
TM 5.0 -> TBD
changing to enhancement since it behaves exactly as designed. adding some kind of notification is an enhancement
producing a message can be handled at the j2eeserver level. producing a good message will probably require an API change in org.netbeans.modules.j2ee.deployment.plugins.spi.StartServer sending back to j2eeserver
The app server is not supported anymore.