2006/11/14, Tim Ellison <[EMAIL PROTECTED]>:
Jimmy, Jing Lv wrote:
> However IMO it was "Support_PortManager.getNextPort()" cause the
> problem. This method, as we already know, is unsafe. Thus the test is
> not stable sometimes, though it appears in-frequently.

Agreed, I've mentioned this before.

> We may find a way to fix it, e.g, try to bind to an available port,
> check if successful.
The tests should be modified to bind to port zero and let the OS
allocate the next available port.
+1

Reply via email to