Unless you don't mismatch ports and the port is actually an http port, not an https port: This is clearly a purely SSL related problem. SSL client and server don't seem to match. (For example, SSL 1 client, and SSL 2 server, or vice versa.) Sorry, but I don't think that this list may help in that case.
Jochen On Mon, Oct 26, 2009 at 6:43 PM, Daphna Wasserman (dwasserm) <[email protected]> wrote: > Hi, > > We are using XML-RPC version 3.1.1 with SSL in our application. > > We have been receiving the following XMLRpc exceptions, and are unable > to figure them out, as we cannot determine which request caused it or by > whom it was sent (dozens of XML-RPC requests are sent in 1 min). > > ERROR [10 26 2009 13:32:55.739 IST] - server.XmlRpcErrorLogger - > Unsupported SSL v2.0 ClientHello > javax.net.ssl.SSLException: Unsupported SSL v2.0 ClientHello > . > . > ERROR [10 26 2009 13:32:55.771 IST] -- server.XmlRpcErrorLogger - Remote > host closed connection during handshake > javax.net.ssl.SSLHandshakeException: Remote host closed connection > during handshake > . > . > .Caused by: java.io.EOFException: SSL peer shut down incorrectly > . > . > ERROR [10 26 2009 13:32:55.858 IST] - server.XmlRpcErrorLogger - Failed > to parse XML-RPC request: Premature end of file. > org.apache.xmlrpc.XmlRpcException: Failed to parse XML-RPC request: > Premature end of file. > . > . > .Caused by: > org.xml.sax.SAXParseException: Premature end of file. > > Is there anyway we can better understand the source/cause of these > errors? > > Thanks > Daphna > > > -- Germanys national anthem is the most boring in the world - how telling!
