Logging Assumptions

Gavlan depends on reading the stdout of the server processes to identify when they change state (this allows the tool to work as little more than a mechanical turk - interacting with the servers as a human would with no special hooks into them).

This means that custom server logging options may break the ability for Galvan to determine the states of servers. This commonly manifests as an indefinite hang immediately at the start of a test run, with Galvan waiting for servers to enter known states.

Specifically, the logging Galvan is expecting to read from the stdout is currently hard-coded in ServerProcess.java in the method called buildEventingStream. If this hang is observed and the stdout.log file does not include these specific strings, a custom logger configuration is likely to blame.