Independent of the actual cause of your local problem I like to mention that it is a severel *architectural* fault if the complete server is hanging just because of one service missing a resource. Since it can always happen that a component has a failure, the server should be prepared for this situation and post a clear message ("Cannot start service X since it is dependend of service Y which caused an exception."). But just doing nothing is not good.
> -----Original Message-----
> From: Timothy.Quinn_at_Sun.COM [mailto:Timothy.Quinn_at_Sun.COM]
> Sent: Mittwoch, 2. Dezember 2009 22:20
> To: dev_at_glassfish.dev.java.net
> Subject: Recently updated and rebuilt trunk workspace, server won't
> start
>
> Hi.
>
> I've updated my v3 trunk workspace and rebuilt, and the server does not
> start. It starts to start (the log stops after the "INFO: Successfully
> launched in 27 msec." message).
>
> When I use
>
> asadmin start-domain --verbose
>
> I see the reason why: many errors caused by this:
>
> Caused by: org.osgi.framework.BundleException: Unresolved constraint in
> bundle com.sun.grizzly.grizzly-config [95]: package;
> (&(package=com.sun.hk2.component)(version>=1.0.0))
>
>
> Is this a case of me needing to wait for a maven repository to be
> updated, or is there something more serious here?
>
> Is anyone else seeing this?
>
> - Tim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
____________
Virus checked by G DATA AntiVirus
Version: AVB 19.525 dated 27.10.2009
Virus news: www.antiviruslab.com