MariaDbEnvironment checked for MARIADB_ALLOW_EMPTY_PASSWORD, which the
official MariaDB image does not support. The documented variable is
MARIADB_ALLOW_EMPTY_ROOT_PASSWORD. As a result, a compose service that
used the documented variable started fine but Spring Boot failed with
"No MariaDB password found".
See gh-51870
Signed-off-by: ohchanKyu <okc0202@naver.com>
Closes gh-51847
* dependabot/github_actions/jfrog/setup-jfrog-cli-5.2.0:
Polish "Bump jfrog/setup-jfrog-cli from 5.1.0 to 5.2.0"
Bump jfrog/setup-jfrog-cli from 5.1.0 to 5.2.0
Closes gh-51846
* dependabot/github_actions/Homebrew/actions/setup-homebrew-2026.09.21.1:
Bump Homebrew/actions/setup-homebrew from 2026.09.13.1 to 2026.09.21.1
Restructured to spring.cache.caffeine.cache-mode with an enum that can
be "native" or "async". Also clarified in the documentation the scope
of the property and that custom caches are not affected.
See gh-51844
CaffeineCacheManager supports asynchronous caches backed by Caffeine's
AsyncCache via setAsyncCacheMode, which adds support for Cache.retrieve.
Add a spring.cache.caffeine.async property (default false) wired to
CaffeineCacheManager.setAsyncCacheMode in CaffeineCacheConfiguration.
See gh-51844
Signed-off-by: seonghun lee <harrisleesh@gmail.com>
Closes gh-51841
* devtools-isdeleted-uri-once:
Polish "Check resource existence once when looking for deleted files"
Check resource existence once when looking for deleted files
ClassLoaderFilesResourcePatternResolver.isDeleted() calls
resource.exists() and resource.getURI() inside the loop over the
uploaded files, so both are repeated once per DELETED entry although
neither depends on the entry. Every resource lookup made while the
application context is being built goes through this method - about
1300 times per restart in the application I measured - so a session
that has accumulated 100 deleted files performs around 130 000 file
system lookups where 1300 are enough.
This commit hoists both calls out of the loop: the resource is
inspected at most once per call, on the first DELETED entry, and the
URI comparison then uses the cached value. The method still returns on
the first match and still reports a failing getURI() as an
IllegalStateException, so behaviour is unchanged.
The loop now walks the per-directory entry sets, which is what
ClassLoaderFiles.addAll() and RestartServer already do, instead of the
flattened view added in gh-46289. That view is wrapped in
Collections.unmodifiableSet(), whose iterator is shared JDK code; in a
running application its delegate calls are megamorphic and C2 stops
inlining them, which made restarts with many accumulated files and no
deletions slower than before gh-46289. isDeleted() returns a boolean,
so the visiting order of the entries cannot change its result.
Measured on a Spring Boot application driven through the remote restart
path (restart request to ApplicationReadyEvent), 12 JVMs per variant
and 20 restarts per JVM, medians:
100 source directories, 10 000 entries, 10 deleted: 278 ms -> 200 ms
100 source directories, 10 000 entries, 100 deleted: 891 ms -> 201 ms
100 source directories, 10 000 entries, 500 deleted: 3536 ms -> 200 ms
100 source directories, 50 000 entries, none deleted: 431 ms -> 341 ms
100 source directories, 10 000 entries, none deleted: 202 ms -> 192 ms
no uploaded files: 150 ms -> 148 ms
See gh-51841
Signed-off-by: DongHoon Lee <dhl1924@naver.com>
Add a new configuration property to prevent the application from
starting when configuration keys that need to be migrated are
found.
With `on-error`, the application fails when keys that are no longer
supported are found. With `on-warning`, it also fails when keys that
have been renamed are found. The default, `never`, keeps the current
behavior of only logging the report.
See gh-51855
Signed-off-by: Hyunwoo Jung <hyunwoojung@kakao.com>
Stéphane Nicoll
ohchanKyu
Hyunwoo Jung
crapxxi
Tran Ngoc Nhan
dependabot[bot]
seonghun lee
Dmitry Sulman
DongHoon Lee
Phillip Webb
itaekyung