- 
                Notifications
    You must be signed in to change notification settings 
- Fork 41.6k
Spring Boot 2.1.0 M1 Configuration Changelog
Configuration properties change between 2.0.4.RELEASE and 2.1.0.M1
| Key | Default value | Description | 
| 
 | 
 | Maximum time that a response can be cached. | 
| 
 | 
 | Whether to enable the caches endpoint. | 
| 
 | 
 | Maximum time that a response can be cached. | 
| 
 | 
 | Whether to enable the integrationgraph endpoint. | 
| 
 | Common tags that are applied to every meter. | |
| 
 | 
 | Whether static resource caching is permitted for this web application. | 
| 
 | 
 | Whether to block when a connection is requested and the pool is full. | 
| 
 | 
 | Blocking period before throwing an exception if the pool is still full. | 
| 
 | 
 | Whether to create a connection on startup. | 
| 
 | 
 | Whether a PooledConnectionFactory should be created, instead of a regular ConnectionFactory. | 
| 
 | 
 | Connection expiration timeout. | 
| 
 | 
 | Connection idle timeout. | 
| 
 | 
 | Maximum number of pooled connections. | 
| 
 | 
 | Maximum number of active sessions per connection. | 
| 
 | 
 | Reset the connection when a "JMSException" occurs. | 
| 
 | 
 | Time to sleep between runs of the idle connection eviction thread. | 
| 
 | 
 | Whether to use only one anonymous "MessageProducer" instance. | 
| 
 | ||
| 
 | Credentials password. | |
| 
 | Comma-separated list of the Elasticsearch instances to use. | |
| 
 | Credentials username. | |
| 
 | ||
| 
 | ||
| 
 | ||
| 
 | ||
| 
 | ||
| 
 | ||
| 
 | Jackson visibility thresholds that can be used to limit which methods (and fields) are auto-detected. | |
| 
 | 
 | Whether to cache message consumers. | 
| 
 | 
 | Whether to cache sessions. | 
| 
 | 
 | Whether to cache message producers. | 
| 
 | 
 | Size of the session cache (per JMS Session type). | 
| 
 | Location of the key store file. | |
| 
 | Store password for the key store file. | |
| 
 | Location of the trust store file. | |
| 
 | Store password for the trust store file. | |
| 
 | Location of the key store file. | |
| 
 | Store password for the key store file. | |
| 
 | Location of the trust store file. | |
| 
 | Store password for the trust store file. | |
| 
 | Location of the key store file. | |
| 
 | Store password for the key store file. | |
| 
 | Location of the trust store file. | |
| 
 | Store password for the trust store file. | |
| 
 | Location of the key store file. | |
| 
 | Store password for the key store file. | |
| 
 | Location of the trust store file. | |
| 
 | Store password for the trust store file. | |
| 
 | 
 | Name of table to use for tracking concurrent Liquibase usage. | 
| 
 | 
 | Name of table to use for tracking change history. | 
| 
 | Schema to use for Liquibase objects. | |
| 
 | Tablespace to use for Liquibase objects. | |
| 
 | 
 | Whether rollback should be tested before update is performed. | 
| 
 | 
 | Whether bean definition overriding, by registering a definition with the same name as an existing definition, is allowed. | 
| 
 | 
 | Path of the dispatcher servlet. | 
| 
 | 
 | Whether to automatically start the scheduler after initialization. | 
| 
 | 
 | Whether configured jobs should overwrite existing job definitions. | 
| 
 | 
 | Name of the scheduler. | 
| 
 | 
 | Delay after which the scheduler is started once initialization completes. | 
| 
 | 
 | Whether to wait for running jobs to complete on shutdown. | 
| 
 | 
 | Whether to enable resolution of already compressed resources (gzip, brotli). | 
| Key | Replacement | Reason | 
| 
 | 
 | |
| 
 | Number of sockets per node against the query (N1QL) service. | |
| 
 | Number of sockets per node against the view service. | |
| 
 | ||
| 
 | ||
| 
 | ||
| 
 | ||
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 |