{{ message }}
Improve logging for LinkageError scenarios involving the LMAX Disruptor library#4124
Merged
vy merged 6 commits intoMay 29, 2026
Merged
Conversation
…n and add tests for error logging
vy
requested changes
May 21, 2026
vy
left a comment
vy
left a comment
Member
There was a problem hiding this comment.
Added defensive LinkageError handling in DisruptorUtil when creating async logger exception handlers.
I don't see that.
Guarded sequenceCallback.set(sequence) with a null check in RingBufferLogEventHandler4 to prevent NPE when callback is not initialized.
I don't see that either.
github-project-automation
Bot
moved this from Approved
to Changes requested
in Log4j pull request tracker
vy
reviewed
May 21, 2026
Contributor
Author
vy
requested changes
May 28, 2026
vy
left a comment
vy
left a comment
Member
There was a problem hiding this comment.
@ramanathan1504, would you mind adding a brief changelog entry, please?
I'd appreciate it if you can update the description of the PR to reflect the goal.
…nitialization to improve diagnostics and user visibility
Contributor
Author
vy
reviewed
May 29, 2026
vy
changed the title
LinkageError scenarios involving the LMAX Disruptor library
vy
approved these changes
May 29, 2026
github-project-automation
Bot
moved this from Changes requested
to Approved
in Log4j pull request tracker
github-project-automation
Bot
moved this from Approved
to Merged
in Log4j pull request tracker
vy
pushed a commit
that referenced
this pull request
Jun 1, 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
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.
FIxes #2250
Reference URLs
What was done
-Improves user visibility by updating the logging message while keeping the existing initialization error handling behavior unchanged.