Hello John,
this is known issue, but it's difficult to catch it, as it happens
rarely and not on all OSs/versions.
Which OS are you using?
Thank you.
WBR,
Alexey.
John C. Turnbull wrote:
>
> I am looking at Grizzly for the first time and I have checked out the
> modules and built the project using NetBeans 6.0. Unfortunately, the
> build failed all because of the failure of one particular unit test.
> The details are:
>
>
>
> -------------------------------------------------------------------------------
>
> Test set: com.sun.grizzly.http.HttpRedirectorTest
>
> -------------------------------------------------------------------------------
>
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 20.92
> sec <<< FAILURE!
>
> testHttpsProtocolProcess(com.sun.grizzly.http.HttpRedirectorTest)
> Time elapsed: 6.705 sec <<< ERROR!
>
> javax.net.ssl.SSLHandshakeException: Remote host closed connection
> during handshake
>
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:808)
>
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096)
>
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
>
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1107)
>
> at
> sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:405)
>
> at
> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:832)
>
> at
> sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
>
> at
> com.sun.grizzly.http.HttpRedirectorTest.testHttpsProtocolProcess(HttpRedirectorTest.java:257)
>
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
>
> at
> com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333)
>
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)
>
> ... 34 more
>
>
>
>
>
> Should I be concerned about this? Is it a known problem? Is there a
> workaround?
>
>
>
> Thanks,
>
>
>
> -JCT
>
>
>