I'm also seeing this same behavior in the V3 nightly build (platform
independent bundle) dated 7/13.
One thing I noticed is that there appears to be new 0 length domain
files being created in domains/domain1/config during start-domain. Not
sure if this is relevant or not but it looks like new behavior to me.
0 Jul 13 08:45 domain3548681432361513674.xml
0 Jul 13 08:45 domain3705159200924962819.xml
0 Jul 13 08:45 domain5059325821941310907.xml
0 Jul 13 08:45 domain8051701864158873548.xml
-ryano
Naresh wrote:
> Hi,
>
> I see that in the latest nightly GlassFish V3 Preview bundle,
> "asadmin start-domain" fails with the following message:
> ------------------------------------------------------------------------------------------------------------------------------
>
> Domain (domain1) did not respond in 90 seconds. It means it is still
> coming up
> or it has failed to come up. Check server.log for details.
> ----------------------------------------------------------------------------------------------------------------------------
>
> The server log shows some ClassNotFoundException(s) stack traces.
>
> Is it some regression which has come in recently?
>
> Note: Its a fresh installation without any modifications using the UC.
>
> Thanks,
> Naresh
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net