Re: [jetty-users] "early EOF" warning when https call from old applicati

[Greg Wilkins <gregw@xxxxxxxxxxx>]

lamphus,

you have a situation that is rather: a) special; b) complex; c) dated

It it going to be hard to help via open source channels, but we will attempt.

You have an application using a jetty-8.1.16 client to talk to a jetty-9.2.9 server and logs an EarlyEoF exception on the server and a "functional issue" in the application.

EarlyEOF is just an indication that the server was parsing a request and the EOF arrived. Typically this is because the client gave up - either it timed out or some other problem happened.

Does this happen on all requests, or just some requests.

Do you know the time the request was issued vs the time the "functional issue" occurs and the earlyEOF logged? Is there a delay.

Can you run the client stand alone talking to the server rather than talking to itself?

regards

--

Greg Wilkins <gregw@xxxxxxxxxxx> CTO http://webtide.com