[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-dev] Many "Broken Pipe" exceptions on Jetty 9.4.12 - HTTP/2.0
|
Hi,
On Thu, Oct 4, 2018 at 10:52 AM Michele Rossi <michele.rossi@xxxxxxxxx> wrote:
>
> hi all,
> I am getting a lot of exceptions like the one below since upgrading to 9.4.12 on Java 10:
>
> java.io.IOException: Broken pipe
> at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.flush(SslConnection.java:847)
> at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:393)
> at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:349)
> at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.lambda$fill$1(SslConnection.java:650)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Suppressed: java.lang.Throwable: HttpInput failure
> at org.eclipse.jetty.server.HttpInput.failed(HttpInput.java:826)
> at org.eclipse.jetty.http2.server.HttpChannelOverHTTP2.onFailure(HttpChannelOverHTTP2.java:323)
> at org.eclipse.jetty.http2.server.HTTP2ServerConnection.onStreamFailure(HTTP2ServerConnection.java:219)
> at org.eclipse.jetty.http2.server.HTTP2ServerConnection.onSessionFailure(HTTP2ServerConnection.java:258)
> at org.eclipse.jetty.http2.server.HTTP2ServerConnectionFactory$HTTPServerSessionListener.onFailure(HTTP2ServerConnectionFactory.java:127)
> at org.eclipse.jetty.http2.HTTP2Session.notifyFailure(HTTP2Session.java:1175)
> at org.eclipse.jetty.http2.HTTP2Session.abort(HTTP2Session.java:1079)
> at org.eclipse.jetty.http2.HTTP2Flusher.onCompleteFailure(HTTP2Flusher.java:331)
> at org.eclipse.jetty.util.IteratingCallback.failed(IteratingCallback.java:401)
> at org.eclipse.jetty.io.WriteFlusher.fail(WriteFlusher.java:319)
> at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:376)
> ... 4 common frames omitted
>
>
> Does this happen because people close their browsers?
This happens when the client closes the connection abruptly during handshakes.
> Is there any way to make it less prominent in the logs?
At what log level is this logged?
> If instead this indicates a more serious problem then I'd like to fix it properly.
I don't think it indicates a serious problem.
The client is just shutting down a connection in the middle of a handshake.
I would not be surprised browsers do this to know what TLS
protocols/ciphers the server support.
--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
