- 
                Notifications
    You must be signed in to change notification settings 
- Fork 41.6k
Spring Boot 2.1.0 M2 Configuration Changelog
Configuration properties change between 2.1.0.M1 and 2.1.0.M2
| Key | Replacement | Reason | 
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | 
| Key | Default value | Description | 
| 
 | 
 | Timeout for getting the Bucket information from the server. | 
| 
 | 
 | Maximum amount of request body to swallow. | 
| 
 | 
 | Maximum number of pooled sessions per connection in the pool. | 
| 
 | 
 | Maximum number of pooled sessions per connection in the pool. | 
| 
 | 
 | Bootstrap mode for JPA repositories. | 
| 
 | 
 | Whether logging of (potentially sensitive) request details at DEBUG and TRACE level is allowed. | 
| 
 | 
 | Whether unique runtime object names should be ensured. | 
| 
 | 
 | Whether to enable Spring’s FormContentFilter. | 
| 
 | 
 | Whether to enable Spring’s HiddenHttpMethodFilter. | 
| 
 | Name of the default queue to receive messages from when none is specified explicitly. | |
| 
 | JSON Web Key URI to use to verify the JWT token. | |
| 
 | 
 | Whether core threads are allowed to time out. | 
| 
 | 
 | Core number of threads. | 
| 
 | 
 | Time limit for which threads may remain idle before being terminated. | 
| 
 | Maximum allowed number of threads. | |
| 
 | Queue capacity. | |
| 
 | 
 | Prefix to use for the names of newly created threads. | 
| 
 | 
 | Maximum allowed number of threads. | 
| 
 | 
 | Prefix to use for the names of newly created threads. | 
| Key | Replacement | Reason | 
| 
 | ||
| 
 | 
 | Whether to create a connection on startup. | 
| 
 | 
 | Connection expiration timeout. | 
| 
 | 
 | Reset the connection when a "JMSException" occurs. | 
| 
 | 
 | Whether to create a connection on startup. | 
| 
 | 
 | Connection expiration timeout. | 
| 
 | 
 | Reset the connection when a "JMSException" occurs. | 
| 
 | 
 | Transaction timeout. | 
| 
 | 
 | Comma-separated list of expiry scanners. | 
| 
 | Transaction object store directory. | |
| 
 | 
 | Whether to enable one phase commit optimization. | 
| 
 | 
 | Interval in which periodic recovery scans are performed. | 
| 
 | 
 | Back off period between first and second phases of the recovery scan. | 
| 
 | Database password to be used by the recovery manager. | |
| 
 | Database username to be used by the recovery manager. | |
| 
 | JMS password to be used by the recovery manager. | |
| 
 | JMS username to be used by the recovery manager. | |
| 
 | Comma-separated list of recovery modules. | |
| 
 | 
 | Unique transaction manager id. | 
| 
 | Comma-separated list of orphan filters. | |
| 
 | 
 |