Cause: Configuration processing was deliberately converting the "default level" to zero.
Consequence: Searching on the configuration error log level returned an unexpected value of zero. This conflicts with the server documentation.
Fix: Do not convert the default log level to zero, but still allow zero to be used to reset the log level to the the default level.
Result: The correct log level is always returned to the client application.