[jetty-users] "early EOF" warning when https call from old application i

[lamphus <perssond9@xxxxxxxxx>]

Hello,

Am running an older application with dependencies on jetty 8.1.16v20140903
(jars: jetty-client, jetty-continuation, jetty-http, jetty-io,
jetty-security, jetty-server, jetty-servlet, jetty-util, jetty-xml). It
works with 8.1.21.v20160908 jars too. It runs inside a jetty 9.2.9.v20150224
without issues using only http. 

When using only https however the application with the jetty 8 deps tries to
httprequest another application in the same container (jetty9) and the issue
reported is :

     [java] 11031 [HttpClient-31] WARN 
org.eclipse.jetty.client.HttpExchange  -
 EXCEPTION adapter1@34ff2b7c=GET//domain:443/application2/rest#WAITING
(1ms)->EXCEPTED(1ms)sent=4ms
     [java] org.eclipse.jetty.io.EofException: early EOF
     [java]     at
org.eclipse.jetty.client.AbstractHttpConnection$Handler.early
EOF(AbstractHttpConnection.java:352)
     [java]     at
org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:3
23)
     [java]     at
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.j
ava:235)
     [java]     at
org.eclipse.jetty.client.AsyncHttpConnection.handle(AsyncHttp
Connection.java:135)
     [java]     at
org.eclipse.jetty.io.nio.SslConnection.handle(SslConnection.j
ava:196)
     [java]     at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectC
hannelEndPoint.java:696)
     [java]     at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectCh
annelEndPoint.java:53)
     [java]     at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedT
hreadPool.java:608)
     [java]     at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedTh
readPool.java:543)
     [java]     at java.lang.Thread.run(Thread.java:745)

and it yields a functional issue.

I've seen something close to it here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=376273 but that issue should
have been vanquished in 8.10+ . 

The older application does not start with 9.2.9.v20150224 jars.

Am not in a position to change the older applications dependencies and am
obviously a newbie with jetty, is there reason to believe the application
needs to be updated with newer dependencies to work well in jetty9 or that
this error would not occur if all applications were living inside a jetty 8
(using https)?


Thanks for any hints.



--
View this message in context: http://jetty.4.x6.nabble.com/early-EOF-warning-when-https-call-from-old-application-in-9-2-9-v2015022er-tp4966218.html
Sent from the Jetty User mailing list archive at Nabble.com.