atom feed18 messages in net.java.dev.glassfish.adminRe: Review of start-domain, stop-dom...
FromSent OnAttachments
Dixie PineOct 7, 2009 3:31 pm.pdf, .pdf, .pdf
Bill ShannonOct 14, 2009 8:54 pm 
Lloyd ChambersOct 14, 2009 10:27 pm 
Byron NevinsOct 14, 2009 11:55 pm 
Dixie PineOct 19, 2009 3:05 pm.pdf, .pdf, .pdf
Bill ShannonOct 19, 2009 3:14 pm 
Lloyd ChambersOct 19, 2009 3:25 pm 
Sankar NeelakandanOct 19, 2009 3:38 pm 
Bill ShannonOct 19, 2009 3:45 pm 
Bill ShannonOct 19, 2009 3:51 pm 
Sankar NeelakandanOct 19, 2009 4:09 pm 
Bill ShannonOct 19, 2009 4:41 pm 
Sankar NeelakandanOct 19, 2009 4:56 pm 
Bill ShannonOct 19, 2009 6:11 pm 
Byron NevinsOct 19, 2009 6:46 pm 
Byron NevinsOct 19, 2009 6:57 pm 
Bill ShannonOct 19, 2009 9:02 pm 
Dixie PineOct 20, 2009 11:11 am.pdf
Subject:Re: Review of start-domain, stop-domain, and restart-domainsman pages
From:Byron Nevins (Byro@Sun.COM)
Date:Oct 19, 2009 6:57:39 pm
List:net.java.dev.glassfish.admin

ccing JFA and JL No way is the server shutting down on my system!

c:\glassfishv3\glassfish>jps 4824 ASMain 4840 admin-cli.jar 4932 ASMain 3864 Jps 4816 admin-cli.jar 5956

================

Based on my results with the browser they are both attached to the same port somehow.

c:\glassfishv3\glassfish>netstat -a -b | grep 8080 TCP vaio:8080 vaio:0 LISTENING 4932 TCP vaio:8080 vaio:0 LISTENING 4824

==================================================

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

[1]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'm not sure why start-domain fails to detect that the server never starts successfully, that's a separate bug.)

--------------------------------------------------------------------- To unsubscribe, e-mail: [2]admi@glassfish.dev.java.net For additional commands, e-mail: [3]admi@glassfish.dev.java.net

--------------------------------------------------------------------- To unsubscribe, e-mail: admi@glassfish.dev.java.net For additional commands, e-mail: admi@glassfish.dev.java.net

References

Visible links 1. http://bt2ws.central.sun.com/CrPrint?id=6157293 2. mailto:admi@glassfish.dev.java.net 3. mailto:admi@glassfish.dev.java.net