I have implemented a custom launcher for GWT so that I can take
advantage of JNDI data sources, authentication, and SSL using the
embedded Jetty server. However, it appears that GWT's hosted browser
does not support connecting to Jetty with SSL configured. I get the
following error:
2009-06-17 11:58:49.671::WARN: EXCEPTION
javax.net.ssl.SSLHandshakeException: Remote host closed connection
during handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord
(SSLSocketImpl.java:801)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake
(SSLSocketImpl.java:1089)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake
(SSLSocketImpl.java:1116)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake
(SSLSocketImpl.java:1100)
at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run
(SslSocketConnector.java:630)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run
(QueuedThreadPool.java:488)
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:782)
... 5 more
To test this I also used launched a stand-a-lone version of Jetty
6.1.11 with SSL enabled and connected to it through GWT's hosted
browser and it fails with the same exception. GWT's hosted browser can
connect without a problem to https://www.amazon.com(after I whitelist
the site). I am going to try and switching from a self-signed
certificate once signed by a CA to see if that matters.
This issue appears to be related to the one I found
athttp://markmail.org/message/jokflzshjidzjtgm#query:%22at%20org.mortbay.jetty.security.SslSocketConnector%24SslConnection.run(SslSocketConnector.java%3A630)%22+page:1+mid:jokflzshjidzjtgm+state:results.
I could not find a bug in Jira with regards to this issue.
Because GWT's hosted browser CAN connect to other SSL sites I am not
sure it is an issue with the hosted browser. However, I can connect to
Jetty's SSL server just fine with Safari on my machine, so I'm really
not in a position to declare whose fault this is.
I also tested this with the most recent version of Jetty 7 and
although the SSL error doesn't appear anymore, the hosted browser will
still not connect to Jetty's SSL server (it is as if the connection
just hangs).
I am using OS X 10.5.6.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
