Sankar Neelakandan wrote on 10/19/09 4:56 PM:
>
>
> Bill Shannon wrote:
>> Sankar Neelakandan wrote on 10/19/09 16:10:
>>>
>>>>>>
>>>>>> Yes, it does not apply to Mac OS.
>>>>>>
>>>>>> However, I believe Byron discovered that it *does* apply to Windows,
>>>>>> right Byron? If so, "Mac OS X" should be replaced with "Windows".
>>>>>> What's not clear to me is whether this is a general property of
>>>>>> Windows (which I still have a hard time believing) or whether it's
>>>>>> a bug in some particular versions of Windows.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> This is a very old bug with windows. Please see a issue from
>>>>> appserver 8.1. It must have been in documentation all along the
>>>>> releases, don't know when windows has been to changed to Mac
>>>>>
>>>>> http://bt2ws.central.sun.com/CrPrint?id=6157293
>>>>
>>>> Is this only a bug with Windows Server versions?
>>> I see this in all versions of windows. Here is how to reproduce .
>>>
>>> asadmin start-domain domain1
>>> asadmin create-domain --adminport 5050 --nopassword --instanceport
>>> 10000 domain2
>>> asadmin create-domain --adminport 6060 --nopassword --instanceport
>>> 10000 domain3
>>> asadmin start-domain domain2
>>> asadmin start-domain domain3
>>
>> If you check the log file, you'll see that domain3 fails to bind to
>> port 10000. The server actually shuts down.
> I see both the domains bind to port 10000 in my machine.
>
> C:\winbug\glassfishv3\glassfish\domains>grep 10000 domain3\logs\server.log
> [#|2009-10-19T16:08:07.343-0700|INFO|glassfish|null|_ThreadID=18;_ThreadName=Thread-3;|Grizzly
> Framework started in: 172ms listening on port 10000|#]
>
> C:\winbug\glassfishv3\glassfish\domains>grep 10000 domain2\logs\server.log
> [#|2009-10-19T16:07:32.000-0700|INFO|glassfish|null|_ThreadID=19;_ThreadName=Thread-3;|Grizzly
> Framework started in: 204ms listening on port 10000|#]
Ok, I reproduced it on Windows XP with my test program. It does require
calling setReuseAddress(true).
Dixie, keep the note, but change from "Mac OS X" to "Windows".