Norman Maurer 36cacc201e Don't bind to a specify port during SSLEngine tests as the port may also be used (#11102) ... Motivation: We should always bind to port 0 to ensure we not try to bind to a port that is already in use during our tests. As we missed to do this in one test we did see test failures sometimes. This showed up here: https://pipelines.actions.githubusercontent.com/obCqqsCMwwGme5y2aRyYOiZvWeJK4O0EY5AYRUDMSELILdqEjV/_apis/pipelines/1/runs/1963/signedlogcontent/18?urlExpires=2021-03-19T12%3A41%3A21.4370902Z&urlSigningMethod=HMACV1&urlSignature=zL6O0msEkghT%2B0hOAL1lqLK66SR0Mp99QIjiau1yPe4%3D Modifications: - Use new InetSocketAddress(0) Result: Fixes possible test failures.		2021-03-19 21:09:46 +01:00
..
src	Don't bind to a specify port during SSLEngine tests as the port may also be used (#11102)	2021-03-19 21:09:46 +01:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2021-03-09 08:18:31 +00:00