Andy Wilkinson e927f52f26 Don’t use findAvailableTcpPort to allocate Undertow a random port ...

Using findAvailableTcpPort is prone to failure when another process
starts using the available port before Undertow starts. This commit
changes UndertowEmbeddedServletContainerFactory to pass the value of
zero down into Undertow where it will ultimately be passed to a
ServerSocket which will then use the underlying OS’s support for binding
to an available port.

Undertow doesn’t provide an API for getting the port(s) on which it’s
listening. Previously, reflection was being used to access the listener
configuration but, when a random port is used, this configuration would
return zero rather than the actual port. The reflective logic has been
updated to look at Undertow’s channels from which the underlying
ServerSocket can be accessed and the local port retrieved

Closes gh-2584

2015-03-04 17:20:06 +00:00

..

main

Don’t use findAvailableTcpPort to allocate Undertow a random port

2015-03-04 17:20:06 +00:00

test

Refine @TestPropertySource locations support

2015-02-26 11:13:34 -08:00