Repository navigation
Upgrade to patched Corretto 21 and increase Metaspace limit - #561
Merged
Merged
Conversation
SoLetsDev
approved these changes
Oct 22, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Upgrade the build and runtime to timezone-patched Amazon Corretto 21.0.12 Alpine, with the Spring Boot and build-tool compatibility updates for Java 21, Sonar Maven scanner 5.8.0.7211, and CI path filters covering the Dockerfile and workflows.
Also increase MaxMetaspaceSize from 100 MB to 300 MB. Course API exhausted the previous cap on its first request after the upgrade; increasing it to 300 MB resolved that failure during rollout.
Validation: the Java 21 migration passed the service test suite, Docker build, non-root execution, and BC/Alberta timezone checks. For the Metaspace follow-up, verified that only the cap changed and git diff --check passed; full endpoint checks were not repeated. Check representative endpoints after deployment and monitor memory usage.