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.

Bug 106586

Summary:	Appserver started twice on JDBC driver deployment
Product:	serverplugins	Reporter:	Nitya Doraisamy <nityad>
Component:	GlassFish	Assignee:	Vince Kraemer <vkraemer>
Status:	RESOLVED WONTFIX
Severity:	blocker	CC:	issues, jbaker, jungi, nouar38, phejl, pjiricka, sherold, tmysik, vkraemer
Priority:	P3	Keywords:	PERFORMANCE
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Bug Depends on:
Bug Blocks:	112110

Description Nitya Doraisamy 2007-06-14 01:48:10 UTC

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.

Comment 1 Nitya Doraisamy 2007-06-14 01:52:46 UTC

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

Comment 2 nouar38 2007-06-22 09:33:42 UTC

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.

Comment 3 Nitya Doraisamy 2007-08-03 02:58:24 UTC

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

Comment 4 Nitya Doraisamy 2007-08-07 19:26:32 UTC

Forgot to downgrade when I updated.

Comment 5 Petr Hejl 2007-10-17 16:21:20 UTC

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.

Comment 6 _ pcw 2008-02-14 01:13:27 UTC

Resolved double start case for debug mode with changeset 67361:7d6164b88bae

Comment 7 Vince Kraemer 2008-04-26 03:16:52 UTC

make sure this doesn't effect v3...

Comment 8 Vince Kraemer 2008-10-18 03:13:59 UTC

let's make sure this doesn't happen with v3.

please be prepared to discuss this issue on 2008/10/22

Comment 9 Nitya Doraisamy 2008-12-12 20:18:06 UTC

This happens both for v3 & v2. This might require changes in deployment code to resolve. Investigating.

Comment 10 Vince Kraemer 2009-09-16 23:55:35 UTC

Assigned engineer: please correct the tm value.  nb 6.7 has shipped, so a tm of
6.7  is invalid at this point