Jetty client EofException problem

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Jetty client EofException problem

Xuefu Zhang
Hi,

We are using Jetty 6.1.26, and encounter a problem with Jetty client, where
an EOF exception is thrown when the client tries to post to a certain
server. To reproduce the problem, I replace the URL in
HttpExchangeTest.testPostWithContentExchange() with the server url we are
having trouble with:
https://post.prospectmtg.com/Post_LeadGenRetail.asp. The test case fails,
with the following in the stdout:

2012-11-28 16:25:10.800:INFO::Logging to STDERR via
org.mortbay.log.StdErrLog
2012-11-28 16:25:10.802:INFO::jetty-6.1.x
2012-11-28 16:25:10.823:INFO::Started SelectChannelConnector@0.0.0.0:45903
2012-11-28 16:25:11.880:WARN::SSL renegotiate denied:
java.nio.channels.SocketChannel[connected local=/192.168.2.100:48240 remote=
post.prospectmtg.com/38.106.58.53:443]
2012-11-28 16:25:11.882:WARN::EXCEPTION on
org.mortbay.jetty.client.ContentExchange@647057258=POST//
post.prospectmtg.com:443/Post_LeadGenRetail.asp#9
org.mortbay.jetty.EofException
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:319)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
    at
org.mortbay.jetty.client.HttpConnection.handle(HttpConnection.java:245)
    at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
    at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
2012-11-28 16:25:12.485:INFO::Graceful shutdown
SelectChannelConnector@0.0.0.0:45903
2012-11-28 16:25:12.988:INFO::Stopped SelectChannelConnector@0.0.0.0:0

The test case itself without changing URL works fine. Also, please note
that if I change the connector type to SOCKET, the test case passes with
the modified URL.

Could any expert give us some remedy/advice on this please? We cannot use SOCKET,
as it gives other problems. Any help is greatly appreciated.

Thanks a lot.

--Xuefu



Reply | Threaded
Open this post in threaded view
|

Re: Jetty client EofException problem

Jesse McConnell
general recommendation is to update to jetty 7 or jetty 8, or even the jetty 9 milestone releases (preferred for you particular case I suspect) which have the new jetty-client api which is much improved and lambda ready for java8


if you absolutely _need_ support on jetty6 then you can always contact webtide.com

jesse

--
jesse mcconnell
[hidden email]


On Thu, Nov 29, 2012 at 6:22 PM, Xuefu Zhang <[hidden email]> wrote:
Hi,

We are using Jetty 6.1.26, and encounter a problem with Jetty client, where
an EOF exception is thrown when the client tries to post to a certain
server. To reproduce the problem, I replace the URL in
HttpExchangeTest.testPostWithContentExchange() with the server url we are
having trouble with:
https://post.prospectmtg.com/Post_LeadGenRetail.asp. The test case fails,
with the following in the stdout:

2012-11-28 16:25:10.800:INFO::Logging to STDERR via
org.mortbay.log.StdErrLog
2012-11-28 16:25:10.802:INFO::jetty-6.1.x
2012-11-28 16:25:10.823:INFO::Started SelectChannelConnector@0.0.0.0:45903
2012-11-28 16:25:11.880:WARN::SSL renegotiate denied:
java.nio.channels.SocketChannel[connected local=/192.168.2.100:48240 remote=
post.prospectmtg.com/38.106.58.53:443]
2012-11-28 16:25:11.882:WARN::EXCEPTION on
org.mortbay.jetty.client.ContentExchange@647057258=POST//
post.prospectmtg.com:443/Post_LeadGenRetail.asp#9
org.mortbay.jetty.EofException
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:319)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
    at
org.mortbay.jetty.client.HttpConnection.handle(HttpConnection.java:245)
    at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
    at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
2012-11-28 16:25:12.485:INFO::Graceful shutdown
SelectChannelConnector@0.0.0.0:45903
2012-11-28 16:25:12.988:INFO::Stopped SelectChannelConnector@0.0.0.0:0

The test case itself without changing URL works fine. Also, please note
that if I change the connector type to SOCKET, the test case passes with
the modified URL.

Could any expert give us some remedy/advice on this please? We cannot use SOCKET,
as it gives other problems. Any help is greatly appreciated.

Thanks a lot.

--Xuefu