Just to clarify, I wasn't starting the same domain twice.
I had two distinct domains (from two distinct server installs, but this
doesn't matter as much) that used the same ports.
The first server instance is fine. The second instance gets
BindExceptions on all the ports (because they are all in use), but the
server is deemed "successfully started". The question is "of what value
is a V3 server instance where Grizzly has failed to start"?
From the perspective of a web developer, I would argue such an instance
is useless and this Grizzly failure should have been treated as a fatal
condition. I suppose there could be some other developer who can use
the server w/o Grizzly (can't imagine who though). I do know that for
NetBeans, failure of Grizzly means no admin access over HTTP, thus it's
fatal for NetBeans regardless.
-Peter
Byron Nevins wrote:
> Yes -- the same domain....
>
>
> Lloyd L Chambers wrote:
>
>> Byron,
>>
>> This one I'm not getting. It is perfectly legitimate to have
>> asadmin start more than one domain; we have always allowed that. Of
>> course, if you mean the same domain then it's pointless--agreed.
>>
>> Lloyd
>>
>> On Jun 25, 2008, at 9:00 AM, byron Nevins wrote:
>>
>>>
>>> A simple addition to asadmin would prevent the same domain from be
>>> started more than once -- asadmin simply runs the "version" command
>>> BEFORE trying to start a domain. If a response is received it
>>> would fail out.
>>> This would be a fine solution for asadmin in any case to make it
>>> more robust. But the onus ought to be on V3 itself. V3 should be
>>> aware that it is already running and refuse to launch another copy
>>> of itself.
>>
>>
>> ---
>> Lloyd L Chambers
>> lloyd.chambers_at_sun.com
>> Sun Microsystems, Inc
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>