logs uncaught errors in AbstractServer#6161
Open
keith-turner wants to merge 1 commit intoapache:2.1from
Open
Conversation
While working apache#6139 caused an exception in the servers main threads that also initiated a halt. The halt seemed to preempt java from printing exceptions from the main thread, so the exception was never seen. This made tracking the bug down more difficult.
keith-turner
changed the title
dlmarion
reviewed
Mar 2, 2026
| log.info(getClass().getSimpleName() + " process shut down."); | ||
| Throwable thrown = err.get(); | ||
| if (thrown != null) { | ||
| log.error("Uncaught exception ", thrown); |
Contributor
There was a problem hiding this comment.
May also want to do the following:
System.err.println("Uncaught execption in AbstractServer.runServer");
thrown.printStackTrace();
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.
While working #6139 caused an exception in the servers main threads that also initiated a halt. The halt seemed to preempt java from printing exceptions from the main thread, so the exception was never seen. This made tracking the bug down more difficult.