ClientAbortException are not suppressed in error logs for the REST API

[arteymix]

This is causing a lot of spam in the Slack channel that collects error logs.

An I/O error has occurred while writing a response message entity to the container output stream. Logger Name org.glassfish.jersey.server.ServerRuntime$Responder Date Sat Feb 14 14:25:38 PST 2026 Level ERROR Thread Name http-nio-8181-exec-33 Source org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:738)

Slack Message

[ppavlidis]

Still applies in Gemma 2.0-alpha: Jersey's ServerRuntime.writeResponse still logs ClientAbortException at ERROR for the REST API, producing slack noise. Needs focused follow-up: register a ClientAbortException-aware filter or ExceptionMapper in gemma-rest that downgrades these to DEBUG/INFO (the client has already gone away; there's nothing to action).

[ppavlidis]

Gemma 2 disposition: Won't fix