Unblu Server Configuration Validation
In order to avoid miss configuration (or configuration that does not have an effect), the unblu server validates it's configuration against the configuration schema.
This document describes how configuration validation works and how it can be configured if required.
2. Default behaviour
If configuration validation is not specially configured, it behaves as follows.
When starting, the unblu server validates the given configuration against it's inherent configuration schema and logs errors (if the configuration is not valid) and warnings (if the configuration not recommended) messages to the log file (see Unblu Server Logging).
If one or more errors are detected, the unblu server will refuse to start up and will deliver 503 responses with status text CONFIGURATION_PROBLEM for all requests.
Configuration validation performs the following validations
- Use of a configuration property that is not defined in the configuration schema -> ERROR
- A configuration value cannot be converted to the expected type according to the configuration schema -> ERROR
- Use of an internal configuration property -> WARNING
- A set of special rules that define dependencies between configuration properties -> WARNING or ERROR
Unblu configuration validation is configurable, the table below shows the most important configuration settings:
|severity||ERROR||severity for use of a configuration property that is not defined|
|severity||WARNING||severity for using internal properties. Possible values are: ERROR, WARNING, IGNORE|
|boolean||false||whether or not unblu should call System.exit if the configuration is not valid (not recommended if using in an application server!)|
|boolean||true||whether or not unblu should deliver 503 responses if configuration is not valid|
|boolean||false||enable/disable configuration validation.|