-
Notifications
You must be signed in to change notification settings - Fork 40.7k
Spring Boot 3.2 Configuration Changelog
Configuration property changes between 3.1.6
and 3.2.0
Key | Replacement | Reason |
---|---|---|
|
|
|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the new InfluxDb Java client provides Spring Boot integration |
|
|
the new InfluxDb Java client provides Spring Boot integration |
|
|
the new InfluxDb Java client provides Spring Boot integration |
|
|
|
|
|
|
|
|
DispatcherServlet property is deprecated for removal and should no longer need to be configured |
Key | Default value | Description |
---|---|---|
|
|
Whether to include the application name in the logs. |
|
Appender pattern for log correlation. |
|
|
|
Whether to export meter metadata (unit and description) to the Dynatrace backend. |
|
Whether observations starting with the specified name should be enabled. |
|
|
Common key-values that are applied to every observation. |
|
|
|
Whether to tag actual query parameter values. |
|
Resource attributes. |
|
|
|
Time unit for exported metrics. |
|
Type of the API token. |
|
|
|
Maximum number of connections that the server accepts and processes at any given time. |
|
||
|
||
|
||
|
Path of the Oracle Kerberos cache file. |
|
|
Whether to enable support for Oracle SQL*Plus commands. |
|
|
Whether to issue a warning rather than an error when a not-yet-supported Oracle SQL*Plus statement is encountered. |
|
|
Location of the Oracle Wallet, used to sign in to the database automatically. |
|
|
Whether transactional advisory locks should be used. |
|
|
Path to the SQL Server Kerberos login file. |
|
|
|
Whether schema should be compared to the application to detect missing mappings. |
|
Jackson on/off features for enums. |
|
|
Jackson on/off features for JsonNodes. |
|
|
Minimum number of concurrent consumers. |
|
|
|
Acknowledge mode of the listener container. |
|
Whether the listener container should use transacted JMS sessions. |
|
|
|
Acknowledge mode used when creating sessions. |
|
|
Whether to use transacted sessions. |
|
Name of the SSL bundle to use. |
|
|
Name of the SSL bundle to use. |
|
|
Whether to instruct the container to change the consumer thread name during initialization. |
|
|
|
Whether to enable observation. |
|
Name of the SSL bundle to use. |
|
|
Name of the SSL bundle to use. |
|
|
Name of the SSL bundle to use. |
|
|
|
Whether to enable observation. |
|
Whether to print a summary of the update operation. |
|
|
Where to print a summary of the update operation. |
|
|
|
Whether to keep the application alive even if there are no more non-daemon threads. |
|
Authentication parameter(s) as a map of parameter names to parameter values. |
|
|
Fully qualified class name of the authentication plugin. |
|
|
|
Duration to wait for a connection to server to be established. |
|
|
Server response read time out for any request. |
|
|
Server request time out for any request. |
|
Pulsar web URL for the admin endpoint in the format '(http or https)://host:port'. |
|
|
Authentication parameter(s) as a map of parameter names to parameter values. |
|
|
Fully qualified class name of the authentication plugin. |
|
|
|
Duration to wait for a connection to a broker to be established. |
|
Client lookup timeout. |
|
|
|
Client operation timeout. |
|
|
Pulsar service URL in the format '(pulsar or pulsar+ssl)://host:port'. |
|
Name of the dead topic where the failing messages will be sent. |
|
|
Name of the initial subscription of the dead letter topic. |
|
|
|
Maximum number of times that a message will be redelivered before being sent to the dead letter queue. |
|
Name of the retry topic where the failing messages will be sent. |
|
|
Consumer name to identify a particular consumer from the topic stats. |
|
|
|
Priority level for shared subscription consumers. |
|
|
Whether to read messages from the compacted topic rather than the full message backlog. |
|
|
Whether to auto retry messages. |
|
Position where to initialize a newly created subscription. |
|
|
Subscription mode to be used when subscribing to the topic. |
|
|
Subscription name for the consumer. |
|
|
Determines which type of topics (persistent, non-persistent, or all) the consumer should be subscribed to when using pattern subscriptions. |
|
|
Subscription type to be used when subscribing to a topic. |
|
|
Topics the consumer subscribes to. |
|
|
Pattern for topics the consumer subscribes to. |
|
|
List of mappings from message type to topic name and schema info to use as a defaults when a topic name and/or schema is not explicitly specified when producing or consuming messages of the mapped type. |
|
|
|
Whether to enable function support. |
|
|
Whether to stop processing further function creates/updates when a failure occurs. |
|
|
Whether to throw an exception if any failure is encountered during server startup while creating/updating functions. |
|
|
Whether to throw an exception if any failure is encountered during server shutdown while enforcing stop policy on functions. |
|
|
Whether to record observations for when the Observations API is available and the client supports it. |
|
SchemaType of the consumed messages. |
|
|
Type of access to the topic the producer requires. |
|
|
|
Whether to automatically batch messages. |
|
|
Whether to enable caching in the PulsarProducerFactory. |
|
|
Time period to expire unused entries in the cache. |
|
|
Initial size of cache. |
|
|
Maximum size of cache (entries). |
|
|
Whether to split large-size messages into multiple chunks. |
|
Message compression type. |
|
|
Message hashing scheme to choose the partition to which the message is published. |
|
|
Message routing mode for a partitioned producer. |
|
|
Name for the producer. |
|
|
|
Time before a message has to be acknowledged by the broker. |
|
Topic the producer will publish to. |
|
|
Reader name. |
|
|
|
Whether to read messages from a compacted topic rather than a full message backlog of a topic. |
|
Subscription name. |
|
|
Prefix of subscription role. |
|
|
Topis the reader subscribes to. |
|
|
|
Whether to record observations for when the Observations API is available. |
|
|
Whether the container (when stopped) should stop immediately after processing the current message or stop after processing all pre-fetched messages. |
|
|
Whether the container (when stopped) should stop immediately after processing the current message or stop after processing all pre-fetched messages. |
|
|
Maximum size of the body of inbound (received) messages. |
|
SSL bundle name. |
|
|
Virtual host of a RabbitMQ instance with the Stream plugin enabled. |
|
|
|
Context Propagation support mode for Reactor operators. |
|
|
Whether the websocket compression extension is enabled. |
|
|
Whether to proxy websocket ping frames or respond to them. |
|
|
Maximum allowable frame payload length. |
|
Sub-protocols to use in websocket handshake signature. |
|
|
|
Whether to resolve the multipart request strictly complying with the Servlet specification, only to be used for "multipart/form-data" requests. |
|
|
Quiet period, after which changes are detected. |
|
Set the maximum number of parallel accesses allowed. -1 indicates no concurrency limit at all. |
|
|
Set the maximum number of parallel accesses allowed. -1 indicates no concurrency limit at all. |
|
|
|
Whether to use virtual threads. |
Key | Replacement | Reason |
---|---|---|
|
|
|
|
|
|
|
|
|
|
Deprecated for removal in Reactor Netty. |
|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
|
|
|
Deprecated for removal in Spring MVC. |