Skip to content

203 Client disconnect exception - #205

Open
simonoakesepimorphics wants to merge 3 commits into
masterfrom
bug/203-client-disconnect-ex-log
Open

203 Client disconnect exception#205
simonoakesepimorphics wants to merge 3 commits into
masterfrom
bug/203-client-disconnect-ex-log

Conversation

@simonoakesepimorphics

Copy link
Copy Markdown
Contributor

Branched from #204
Remap Tomcat internal logs to slf4j.

@der der left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like a reasonable thing to do but doesn't seem to address the SEVERE exception.

@simonoakesepimorphics

Copy link
Copy Markdown
Contributor Author

Added an interceptor to log the exception as a warning instead.

@der der left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, didn't realise you intercept any write that way!

Approving now, but see comment on reduce unnecessary log volume.

context.proceed();
} catch (Exception e) {
if (e.getCause() instanceof ClientAbortException) {
log.warn("Client interrupted response writer.", e);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Think this will put the whole exception stack trace in the log which we don't want. Suggest just appending the exception message.

Base automatically changed from tech/major-security-updates to master June 11, 2026 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants