Do not specify a JVM garbage collector if none specified in the Coherence yaml #760
Conversation
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
oracle-contributor-agreement
bot
added
the
OCA Verified
|
tmiddlet2666
approved these changes
Jun 11, 2025
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.
The Operator used to set the JVM arg
-XX:+UseG1GCif nothing was specified for thespec.jvm.gc.collectorfield. This meant that it was impossible to set a collector that the Operator yaml did not recognise as this would cause two-XX:+Use***JVM args and the JVM would not start.If the
spec.jvm.gc.collectoris not set the Operator does not set any GC collector JVM arg. Thespec.jvm.gc.collectorfield now also supportsserialandzgcas additional values.