The trivial test results are the same for me. Grizzly is clearly
different then simple ServerSocket usage
Here is how I reproduce it:
1) have a stock domain1 -- not running
2) create domain2 with a different admin port (e.g. 5050) but the same
instance port (8080) [1]
2B) I edit index.html for both domains. Simple test -- add
<h1>domain1</h1> or <h1>domain2</h1>
respectively
3) start domain1
4) start domain2
On Windows step 4 works with no errors. [2]
- Now go to a browser and load localhost:8080.
- One of the domains will be chosen - usually the second one
started -- and it will not switch. You can reload over and over.
- Now kill the domain that "owns" 8080.
- The browser silently and without any hiccup will switch to using
the other domain
I edit index.html for both domains. Simple test -- add
<h1>domain1</h1> <h1>domain2</h1> respectively
[1] asadmin create-domain --adminport 5050 --instanceport 8080 domain2
[2] btrace jvm bind error. Not fatal. I set monitoring-enabled to
false to avoid the problem
Bill Shannon wrote:
Lloyd
Chambers wrote on 10/19/09 15:26:
See these flags. I do not know what they
mean for sure, but they imply re-opening is possible.
I don't know what that's about, but a simple test shows that only
a single process can open a server socket on a given port on Mac OS X.
I tried the same test on Windows XP with the same behavior.
I used a trivial test program that does "new ServerSocket(10010)"
and then sleeps, then I try to run two of those programs at once.
The second instance fails, as expected, on Mac OS and Windows.
Byron, how did you reproduce this issue?
---------------------------------------------------------------------
To unsubscribe, e-mail: admin-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: admin-help@glassfish.dev.java.net