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)
Created attachment 48552 [details]
this is pretty contrived use-case.
PCW: is this (or something similar) an issue for the v3 plugin?
I will check it for v3 and react accordingly....
this looks like a problem for v3 also... fixing for v3 in for 7.0
Is this really not working in V3? I would have expected it to work.
I just tried it and was not successful... I am doing more investigation.
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
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
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
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.