SocketWrapperTest and HostAddressServiceTest fails to often

[GoogleCodeExporter]

What steps will reproduce the problem?

1. run ant test in commons
2. randomly SocketWrapperTest or HostAddressServiceTest fails
3.

What is the expected output?
[junit] Running com.continuent.tungsten.common.network.HostAddressServiceTest
[junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.622 
sec
[junit] Running com.continuent.tungsten.common.sockets.SocketWrapperTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.889 
sec

What do you see instead?
[junit] Running com.continuent.tungsten.common.network.HostAddressServiceTest
[junit] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.591 
sec
[junit] Test com.continuent.tungsten.common.network.HostAddressServiceTest 
FAILED
[junit] Running com.continuent.tungsten.common.sockets.SocketWrapperTest
[junit] Tests run: 5, Failures: 0, Errors: 2, Time elapsed: 0.898 sec
[junit] Test com.continuent.tungsten.common.sockets.SocketWrapperTest FAILED

What version of the product are you using?

TR-4.0.0

On what operating system?

Mac OS X

Please provide any additional information below.

Notes:

This happens mostly on a fast computer with multiple cores.

Original issue reported on code.google.com by secs...@gmail.com on 29 Jan 2015 at 7:02

[GoogleCodeExporter]

This issue was updated by revision r2779.

Add thread synchronization.

Original comment by csaba.si...@continuent.com on 29 Jan 2015 at 7:27

[GoogleCodeExporter]

This issue was updated by revision r2780.

Updated comments and added thread synchronization.

Original comment by csaba.si...@continuent.com on 29 Jan 2015 at 8:26

[GoogleCodeExporter]

This issue was updated by revision r2783.

Cleaned up SSL selection logic and added barrier to prevent potential race 
condition on echo server start in order to defeat random SSL unit test failures 
that have been dogging builds.  

Original comment by robert.h...@continuent.com on 5 Feb 2015 at 9:48