An old problem that we already noticed, I guess still there's a lot of tests using getNextPort(). +1 for using port 0
2007/4/18, Nathan Beyer <[EMAIL PROTECTED]>:
For the slow (and lazy), can you point me to one of the tests that just uses port 0. Thanks. -Nathan On 4/17/07, Tim Ellison <[EMAIL PROTECTED]> 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 >
-- Best Regards! Jimmy, Jing Lv China Software Development Lab, IBM
