Bug 115216 - Failed to deploy two applications to stopped server
Failed to deploy two applications to stopped server
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9
6.x
All All
: P4 (vote)
: TBD
Assigned To: Vince Kraemer
issues@serverplugins
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-11 09:41 UTC by Ivan Sidorkin
Modified: 2009-02-20 01:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
:


Attachments
screen shot (5.10 KB, image/png)
2007-09-11 09:42 UTC, Ivan Sidorkin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Sidorkin 2007-09-11 09:41:47 UTC
Product Version: NetBeans IDE 6.0 Beta 1 (Build 200709100000) 
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

- create Enterprise|InterceprorStateless sample
- create Enterprise|AnnotationOverrideIntercepror sample
(or any other projects that will be deployed to GlassFish)
- check that GlassFish stopped
- try to deploy first application
- until server starts try to dewploy second application

server started, but only one application deployed
3 processes running (see attach)
Comment 1 Ivan Sidorkin 2007-09-11 09:42:18 UTC
Created attachment 48552 [details]
screen shot
Comment 2 Vince Kraemer 2007-09-26 06:15:56 UTC
this is pretty contrived use-case.
Comment 3 Vince Kraemer 2008-04-26 03:47:52 UTC
PCW: is this (or something similar) an issue for the v3 plugin?
Comment 4 Vince Kraemer 2008-10-18 03:45:35 UTC
I will check it for v3 and react accordingly....

Comment 5 Vince Kraemer 2008-10-25 03:44:31 UTC
this looks like a problem for v3 also... fixing for v3 in for 7.0
Comment 6 _ pcw 2008-10-25 04:11:25 UTC
Is this really not working in V3?  I would have expected it to work.
Comment 7 Vince Kraemer 2008-10-25 16:36:32 UTC
I just tried it and was not successful... I am doing more investigation.
Comment 8 Vince Kraemer 2008-11-14 00:47:36 UTC
this has a lot to do with the way we handle requests... It seems like they should be going into some kind of queue... or
something...  

The first call to deploy determines that there are two tasks that have to happen... the server needs to start and then
the deploy needs to fire if that is successful.  The first call triggers the start-up...  The second call to deploy
should detect that the server is starting... and wait for that startup to complete before attempting to start the
deployment...

Comment 9 _ pcw 2008-11-14 01:38:03 UTC
Ah yes, now I see why it doesn't work.  Solving the "what to do if the server is in "starting" problem was deliberately
out of scope for the 6.1 plugin and was supposed to be part of reworking the way that thread operates, which as you
know, wasn't completed for 6.5.

I expected that such a use case would be rare, and the work around should be start the server separately, then do both
deploys.
Comment 10 Vince Kraemer 2009-02-20 01:12:53 UTC
it looks like this is not an issue for v3 anymore.  fixing this in the v2 plugin is not p3. when to fix for v2 is an
open question... so resetting the TM to TBD, too.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo