Upgrade log4j to 2.26.0. - #346
Merged
Merged
Conversation
artntek
approved these changes
Jun 8, 2026
artntek
left a comment
artntek
left a comment
Collaborator
There was a problem hiding this comment.
Did you test this in a container? I vaguely remember that the k8s version started failing (even though non-k8s was working OK) after the last time we updated log4j (I think that was maybe in the dataone-indexer repo??)
Collaborator
Author
|
No, I didn't test it on k8s. It was an Metacat issue that the obsoleted elements in the k8s log4j2.properties prevented Metacat starting up. |
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
2 participants
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.
Ticket is here.