The client, asadmin, starts a new process, namely a JVM running V3.
Then asadmin hangs around and waits for a special file to get written by
the server. That is the extent of the communications between client and
server.
You are having problems in the server itself. The file is not getting
written. There are currently about 112 bazillion things that can go
wrong. Unfortunately things that go wrong early will NOT be logged
(this should be doc'd, btw).
Do this:
1) start with "--verbose" --> you will see every bit of stdout and
stderr, guaranteed.
2) look in server.log for clues on what happened - especially look at
the JVM invocation command at the beginning.
3) If 1 and 2 don't help try starting with java -jar glassfish.jar
Paul Davies wrote:
> Hi,
>
> I am trying to start a domain with the latest nightly build (GlassFish
> v3.0-SNAPSHOT (build 74.1)) of GlassFish v3, but the start-domain
> command hangs in a vain search for a nonexistent pid file in the
> domain's config directory.
>
> Anybody else experienced this phenomenon or know what's going on?
>
> Also, should I file an issue?
>
> Thanks!
>
--
Byron Nevins - Sun Microsystems, Inc.
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188