I don't think we'll need to use Quantum Electrodynamics to solve this
riddle.
You have server2 running and it is using port 25848
You then try to start instance1 which also wants to use port 25848.
That's a fatal error.
list-instances is pretty smart. It does not just rely on a host and
port. It also checks for other things that positively ID the instance.
The browser can't do that -- it just connects to the host and port you
give it -- which has instance2 listening...
On 6/21/2010 12:41 PM, Bobby Bissett wrote:
> The CLI says:
>
> hostname%./asadmin start-instance instance1
> Command start-instance executed successfully.
>
> The server (DAS) log says:
>
> [#|2010-06-21T15:37:16.240-0400|INFO|glassfish3.1|null|_ThreadID=41;_ThreadName=Thread-1;|There
> is a process already using the admin port 25848 -- it probably is
> another instance of a GlassFish server.|#]
> [#|2010-06-21T15:37:16.241-0400|INFO|glassfish3.1|null|_ThreadID=41;_ThreadName=Thread-1;|Command
> start-local-instance failed.|#]
>
> So did it work or fail? FWIW, if I then list instances:
>
> hostname%
> /Users/bobby/work/ws/v3/distributions/glassfish/target/glassfishv3/glassfish/bin/asadmin
> list-instances
> instance1 not running
> instance2 running
>
> But hitting the http listener port in a browser shows it's running. So
> it's either running or not running. :)
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188