Thanks for the heads up on this.
Please open a NetBeans issue and describe how to reproduce the problem,
step-by-step.
NetBeans currently starts the server using 'java -jar glassfish.jar
lots-of-blah-blah-blah'
If start-domain is doing additional sanity tests before doing something
similar, those checks are not getting done with the plugin.
vbk
Bobby Bissett wrote:
> Hi all,
>
> After updating a 3.0.1 installation to 3.1, if you try to start the
> server with "asadmin start-domain" then you're told that you need to
> run first with the --upgrade flag and then all is well. If you run the
> update and then start the server through NetBeans, it fails and
> eventually NB tells you "<your server> Start Failed." Log info is below.
>
> Can someone tell me how NB is starting GF? This is an ugly bug,
> especially now that I see that it leaves a Java process running after
> the failures below. That running process leads to another error
> because it prevents the osgi-cache from being renamed when the user
> runs "asadmin start-domain --upgrade." At least that's my suspicion
> about what's going on on the Windows environment where this was
> reported. See comments here:
>
> http://blogs.sun.com/bobby/entry/moving_on_up_upgrading_to#comments
>
> Thanks,
> Bobby