BaSyxHttpServer exposes startup failures now.

BaSyxHttpServer might have silently failed for any number of possible
reasons (e.g. port already in use). This was due to a behavior internal
to tomcat which can be influenced through a system property. This
property is now set, allowing user code to react to startup failures by
inspecting hasEnded() after start() returns.

Also, a race condition between tomcat.notifyAll() and tomcat.wait() has
been fixed.

Signed-off-by: Moritz Marseu <moritz.marseu@festo.com>
Change-Id: Ic4fba417107ac6c8c02b6d94c8371ee503303f5a
1 file changed