Deploying a web application restarts the application server.
Stopping server Sun Java System Application Server
Starting server Sun Java System Application Server
Incrementally deploying CalculatorApplication_localhost:4848_server
Completed incremental distribution of CalculatorApplication
Incrementally redeploying CalculatorApplication_localhost:4848_server
While redeploying, trying to stop the application in target server completed
While redeploying, trying to remove reference for application in target server
deployment started : 0%
deployment finished : 100%
Deploying application in domain completed successfully
Trying to create reference for application in target server completed successfully
Trying to start application in target server completed successfully
Deployment of application CalculatorApplication completed successfully
BUILD SUCCESSFUL (total time: 2 minutes 8 seconds)
Not sure if this is a bug. If the server restart flag was set due to other user actions, the server would restart.
Do you see this on every deploy? What are the actions/steps that were performed before the deploy which caused the restart.
I might have done some config changes does requires a server restart. But I would not expect netbeans to restart it when
I am deploying some application without even a warning. Who is accountable for the downtime in production scenarios.
Many times restart required is just a way to inform the user that the changes he made are effective in the next restart.
For eg, I might have increased the max heap size for the jvm, and that would set the restart required flag. But I
wouldn't want the server to be restarted at my next deploy!!
We assume that a developer wants to see the effect of their changes, soon.
If a developer made a change that sets the restart required flag the IDE will restart the server before running their
app, so they can see the effect of their changes on the app that they are developing.
This assumption may be incorrect for some number of users.
Note: deploying an app from NetBeans onto a production server is not a recommended use-case for NetBeans or a production
About the only way to resolve this is to add a feature to the plugin, to allow the user to control the reaction to the
restart flag that they desire. Other changes would need to be made to account for the new server "state" that the IDE
need would to present to the user.
Converting to a p2 enhancement
this needs to be resolved in the v3 plugin as part of the 7.0 release?
please be prepared to discuss this issue on 2008/10/22
no issue should be assigned to issues. redistributing the load
changes to the v2 plugin are not high priority