Skip to content

After Magnum is updated, update logging to not log at error-level SQL #1516

@adamw

Description

@adamw

Exceptions such as:

backend java.net.SocketException: Closed by interrupt
backend 	at java.base/java.net.Socket$SocketInputStream.read(Socket.java:1106)
backend 	at org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:192)
backend 	at org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:159)
backend 	at org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:144)
backend 	at org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:76)
backend 	at org.postgresql.core.PGStream.receiveChar(PGStream.java:477)
backend 	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2175)
backend 	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:372)
backend 	... 128 common frames omitted
backend Wrapped by: org.postgresql.util.PSQLException: An I/O error occurred while sending to the backend.

which originate from an interruption, should be only DEBUG-log. Such filtering is already present OOTB in NettySyncServerOptions for InterruptedException

Magnum fix to get the right exceptions context: AugustNagro/magnum#126

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions