Note to all --
You will never see any messages before the logging service is
initialized. E.g. if OSGi goes down in flames -- the server will never
"start" and nothing will appear in the log.
If you start with --verbose that is the only way you'll ever see any
early error messages.
I personally only run with the --verbose flag. I like to be able top
"see" my servers running and I can kill them cleanly with a ^C. You
should immediately start with --verbose the moment anything amiss
happens -- like below. It works exactly the same with instances.
On 7/28/2010 8:59 AM, Justin Lee wrote:
> When trying to start a trunk build from this morning I'm back to my
> favorite bug of all time:
>
> /Users/jlee/Downloads/glassfishv3/glassfish/bin/asadmin start-domain
> Waiting for the server to start
> .........................................................................................................................................................................................................................................................................................................
>
>
>
> setting AS_DEBUG=true just yields screen after screen of:
> Check for pid file:
> /Users/jlee/Downloads/glassfishv3/glassfish/domains/domain1/config/pid
>
> server.log stops updating after:
> Jul 28, 2010 11:58:51 AM
> com.sun.enterprise.admin.launcher.GFLauncherLogger info
> INFO: Successfully launched in 28 msec.
>
> Any ideas?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188