-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.io.IOException: Close org.eclipse.jetty.server.HttpConnection$SendCallback@5b27455[PROCESSING] #3652
Comments
This exception indicates that the connection was closed whilst the connection was still trying to write something. Does that tally with your application and scenario? |
The application wasn't shut down or restarted when this exception was thrown. So the connection doesn't seem to be closed by the application. |
ok, what about the other way, the client closing the connection? (not the server) |
Sorry due to legal reason this is the most of the stack trace I could include. The exception is thrown from the handle method of an implementation of AbstractHandler. But I'm pretty sure there is no logic for closing the connection in our implementation. |
And I haven't found any evidence that the client is closing the connection. Normally when that happens our server would log an error. |
I noticed line 427 of IteratingCallback.java was changed from: |
Any update on this? For now we are catching the IOException and ignoring it - probably not the right thing to do, but don't see other choice. |
The exception was changed to IOException because the failure could be other things than a remote close, eg a timeout, OOM, etc. The previous code was loosing the reason for the failure. Thus all we know at this time is that the end-point is being closed. We need more information to decide if that is abnormal or normal. Note that if you need an NDA to reveal more detail, that is part of our normal commercial support offering. |
I checked and we are not able to take commercial support at this time. I'll close the issue and will reach out when we are in a situation to get the commercial support. |
Hi @joakime @gregw -- I am running into similar issue where the same error is output. Our application was in good health at the time of this exception and there was no connection closure by the client. Can someone suggest what can be the cause here?
|
@varmax2511 Jetty 9 is now at End of Community Support.
You should be using a supported version of Jetty at this point in time. And yes, you can run Jetty 12 with |
We observed this exception in the log (with embedded Jetty version 9.4.14.v20181114). I have tried to google it but haven't found any useful information. Is it a known issue?
at org.eclipse.jetty.util.IteratingCallback.close(IteratingCallback.java:427)
at org.eclipse.jetty.server.HttpConnection.onClose(HttpConnection.java:507)
at org.eclipse.jetty.io.ssl.SslConnection.onClose(SslConnection.java:273)
at org.eclipse.jetty.io.SelectorManager.connectionClosed(SelectorManager.java:345)
at org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint.run(ManagedSelector.java:923)
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:834)
java.io.IOException: Close org.eclipse.jetty.server.HttpConnection$SendCallback@5b27455[PROCESSING][i=HTTP/1.1{s=200,h=4,cl=30578},cb=org.eclipse.jetty.server.HttpChannel$CommitCallback@18de03b] in state PROCESSING
at org.eclipse.jetty.util.IteratingCallback.close(IteratingCallback.java:427)
at org.eclipse.jetty.server.HttpConnection.onClose(HttpConnection.java:507)
at org.eclipse.jetty.io.ssl.SslConnection.onClose(SslConnection.java:273)
at org.eclipse.jetty.io.SelectorManager.connectionClosed(SelectorManager.java:345)
at org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint.run(ManagedSelector.java:923)
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:834)
The text was updated successfully, but these errors were encountered: