Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

org.eclipse.jetty.io.EofException: Early EOF	at org.eclipse.jetty.server.HttpInput$3.getError(HttpInput.java:1103)	at org.eclipse.jetty.server.HttpInput$3.noContent(HttpInput.java:1092)	at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:307)	at org.eclipse.jetty.util.IO.copy(IO.java:170)	at org.eclipse.jetty.util.IO.copy(IO.java:122)	at org.eclipse.jetty.http.client.HttpClientContinueTest$14.handle(HttpClientContinueTest.java:397)	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)	at org.eclipse.jetty.server.Server.handle(Server.java:564)	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:368)	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279)	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:112)	at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124)	at org.eclipse.jetty.util.thread.Invocable.invokePreferred(Invocable.java:122)	at org.eclipse.jetty.util.thread.strategy.ExecutingExecutionStrategy.invoke(ExecutingExecutionStrategy.java:58)	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:201)	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produce(ExecuteProduceConsume.java:97)	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:672)	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:590)	at java.lang.Thread.run(Thread.java:745)