Skip to content

Spring Boot 4.1.0 M2 Configuration Changelog

Stéphane Nicoll edited this page Feb 19, 2026 · 2 revisions

Configuration property changes between 4.1.0-M1 and 4.1.0-M2

Deprecated in 4.1.0-M2

Key Replacement Reason

management.dynatrace.metrics.export.v1.device-id

Dynatrace V1 API is deprecated, use the V2 API instead.

management.dynatrace.metrics.export.v1.group

Dynatrace V1 API is deprecated, use the V2 API instead.

management.dynatrace.metrics.export.v1.technology-type

Dynatrace V1 API is deprecated, use the V2 API instead.

Added in 4.1.0-M2

Key Default value Description

management.otlp.metrics.export.compression-mode

none

Compression mode to use when exporting metrics.

management.otlp.metrics.export.publish-max-gauge-for-histograms

Whether to publish a separate gauge for the max value of histogram-based meters.

server.compression.additional-mime-types

``

Comma-separated list of additional MIME types that should be compressed.

spring.datasource.oracleucp.fail-fast-on-chunk-unavailable

spring.datasource.oracleucp.u-c-p-event-listener-provider

spring.jackson.factory.constraints.read.max-document-length

-1

Maximum allowed document length.

spring.jackson.factory.constraints.read.max-name-length

50000

Maximum name length.

spring.jackson.factory.constraints.read.max-nesting-depth

500

Maximum nesting depth.

spring.jackson.factory.constraints.read.max-number-length

1000

Maximum number length.

spring.jackson.factory.constraints.read.max-string-length

20000000

Maximum string length.

spring.jackson.factory.constraints.read.max-token-count

-1

Maximum allowed token count.

spring.jackson.factory.constraints.write.max-nesting-depth

500

Maximum nesting depth.

Removed in 4.1.0-M2

Key Replacement Reason

spring.data.redis.lettuce.cluster.refresh.adaptive

All adaptive triggers are enabled by default.

Clone this wiki locally