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.
JDBC driver deployment on Sun Appserver causes the server to get started twice in a single deploy (if it is not running), once before the JDBC driver deploy code is reached and again if the driver deployment happened and the restart flag is been set.
The deployment code (org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment) attempts to get a target via 'serverInstance.getTargets()[0].getTarget()' which causes a server start if server is not running because it checks if this server needs "needsStartForTargetList" and for Sun AS that is true. Then the api for deploying JDBC drivers is called which in turn sets a restart flag if needed and cause a restart. See 99610 for more info in JDBC driver deployment. One resolution would be to use appserver's libraries option which does not require a restart (available on 9.1, possible 9.0) for those servers. But this issue would still be present for 8.x those servers and avaoid
added myself in this issue. In my case, my instance was already started and after deploying a jdbc resource with my web app, got also a restart. I'll look to 99610 for more details about JDBC driver deployment. nouar.
This has not been raised by users as yet. So we might be able to keep it as is for now. It would be nice to out in the workaround detailed above for 9.1 appserver. Downgrading to P3
Forgot to downgrade when I updated.
Same occurs for starting application in debug mode (and when server is stopped). Server is started (normal mode) to get targets then it is stopped and started in debug mode.
Resolved double start case for debug mode with changeset 67361:7d6164b88bae
make sure this doesn't effect v3...
let's make sure this doesn't happen with v3. please be prepared to discuss this issue on 2008/10/22
This happens both for v3 & v2. This might require changes in deployment code to resolve. Investigating.
Assigned engineer: please correct the tm value. nb 6.7 has shipped, so a tm of 6.7 is invalid at this point