In this case, I guess the rarely used port may be suitable, though it is not perfect and may cause failure (in very little possibility?) Or let's make the test as a special test, as exclude test, or manual test?
I suggest we should never use Support_PortManager any more. 2007/4/19, Ruth Cao <[EMAIL PROTECTED]>:
Tim Ellison wrote: > Ruth Cao wrote: > >> You are right, Vladimir. >> >> It is just because the 'port' variable is set to 8080 and on some >> machines this port has already been occupied. The test case will pass >> if we use Support_PortManager.getNextPort() on my side. >> > > Please don't use the PortManager, just open port 0 and let the OS > allocate a free port. There are examples in the existing tests. > > Regards, > Tim > > Yes, I agree that we should use port 0 in almost all the test cases. However, it seems that this test case is a little bit special. It requires to initialize a ServerSocket to connect 0.0.0.0 after connecting localhost successfully. If we use port 0 and 0.0.0.0 at the same time, the ServerSocket constructed will be invalid. Thus, shall we assign a rarely-used port (e.g. 50000), or continue using Support_PortManager? Any ideas? Suggestions? -- Regards, Ruth Cao China Software Development Lab, IBM
-- Best Regards! Jimmy, Jing Lv China Software Development Lab, IBM
