Http3TestServer should not log an exception stack trace when it is stopping normally

XMLWordPrintable

    • b02

        There is no reason to log the stack trace in this case, it only clutters the logs:

        INFO: QUIC: QuicClientConnection(53) sending CONNECTION_CLOSE frame before entering draining state
        java.io.IOException: QUIC endpoint closed - no error
        at java.net.http/jdk.internal.net.http.quic.TerminationCause.toReportedCause(TerminationCause.java:129)
        at java.net.http/jdk.internal.net.http.quic.TerminationCause.<init>(TerminationCause.java:56)
        at java.net.http/jdk.internal.net.http.quic.TerminationCause$SilentTermination.<init>(TerminationCause.java:203)
        at java.net.http/jdk.internal.net.http.quic.TerminationCause.forSilentTermination(TerminationCause.java:96)
        at java.net.http/jdk.internal.net.http.quic.QuicEndpoint.silentTerminateConnection(QuicEndpoint.java:1281)
        at java.net.http/jdk.internal.net.http.quic.QuicEndpoint.close(QuicEndpoint.java:1351)
        at jdk.httpclient.test.lib.quic.QuicServer.close(QuicServer.java:831)
        at jdk.httpclient.test.lib.http3.Http3TestServer.close(Http3TestServer.java:328)
        at jdk.httpclient.test.lib.http3.Http3TestServer.stop(Http3TestServer.java:157)
        at jdk.httpclient.test.lib.common.HttpServerAdapters$HttpTestServer$H3ServerAdapter.stop(HttpServerAdapters.java:1630)
        at H3MultipleConnectionsToSameHost.test(H3MultipleConnectionsToSameHost.java:313)


              Assignee:
              Daniel Fuchs
              Reporter:
              Daniel Fuchs
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: