You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-dev@ws.apache.org by "Daphna Wasserman (dwasserm)" <dw...@cisco.com> on 2009/10/26 18:43:26 UTC
Vague XML-RPC exceptions
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
Re: Vague XML-RPC exceptions
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Daphna,
is it possible to check the traffic using Wireshark or an HTTP proxy?
Cheers,
Siegfried Goeschl
Daphna Wasserman (dwasserm) 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
>
>
>
>
RE: Vague XML-RPC exceptions
Posted by "Daphna Wasserman (dwasserm)" <dw...@cisco.com>.
Thanks!
-----Original Message-----
From: Jochen Wiedmann [mailto:jochen.wiedmann@gmail.com]
Sent: Wednesday, October 28, 2009 2:39 PM
To: xmlrpc-dev@ws.apache.org
Subject: Re: Vague XML-RPC exceptions
Daphna, we don't have access to that information. All we have is the exception you are seeing. We ask the SSL library for an incoming connection, or get a connection from Tomcat (or whatever servlet engine might be in use). If we get it, fine, if we don't get it, there's an exception.
Jochen
2009/10/28 Daphna Wasserman (dwasserm) <dw...@cisco.com>:
> I understand its an SSL related problem, however I need information on the specific client which sent the bad message (there are dozens XML-RPC requests per minute). There is nothing in the XmlRpcErrorLogger which helps to identify that problematic client request. Can such information be added to the exception ?
>
> Thanks
> Daphna
>
> -----Original Message-----
> From: Jochen Wiedmann [mailto:jochen.wiedmann@gmail.com]
> Sent: Tuesday, October 27, 2009 8:32 PM
> To: xmlrpc-dev@ws.apache.org
> Subject: Re: Vague XML-RPC exceptions
>
> 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) <dw...@cisco.com> 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!
>
--
Germanys national anthem is the most boring in the world - how telling!
Re: Vague XML-RPC exceptions
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Daphna,
I know it is a long shot but the the Charles Web Proxy
(http://www.charlesproxy.com/) supports SSL proxying (see
http://www.charlesproxy.com/documentation/using-charles/ssl-proxying/)
Cheers,
Siegfried Goeschl
Jochen Wiedmann wrote:
> Daphna, we don't have access to that information. All we have is the
> exception you are seeing. We ask the SSL library for an incoming
> connection, or get a connection from Tomcat (or whatever servlet
> engine might be in use). If we get it, fine, if we don't get it,
> there's an exception.
>
> Jochen
>
>
> 2009/10/28 Daphna Wasserman (dwasserm) <dw...@cisco.com>:
>
>> I understand its an SSL related problem, however I need information on the specific client which sent the bad message (there are dozens XML-RPC requests per minute). There is nothing in the XmlRpcErrorLogger which helps to identify that problematic client request. Can such information be added to the exception ?
>>
>> Thanks
>> Daphna
>>
>> -----Original Message-----
>> From: Jochen Wiedmann [mailto:jochen.wiedmann@gmail.com]
>> Sent: Tuesday, October 27, 2009 8:32 PM
>> To: xmlrpc-dev@ws.apache.org
>> Subject: Re: Vague XML-RPC exceptions
>>
>> 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) <dw...@cisco.com> 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!
>>
>>
>
>
>
>
Re: Vague XML-RPC exceptions
Posted by Jochen Wiedmann <jo...@gmail.com>.
Daphna, we don't have access to that information. All we have is the
exception you are seeing. We ask the SSL library for an incoming
connection, or get a connection from Tomcat (or whatever servlet
engine might be in use). If we get it, fine, if we don't get it,
there's an exception.
Jochen
2009/10/28 Daphna Wasserman (dwasserm) <dw...@cisco.com>:
> I understand its an SSL related problem, however I need information on the specific client which sent the bad message (there are dozens XML-RPC requests per minute). There is nothing in the XmlRpcErrorLogger which helps to identify that problematic client request. Can such information be added to the exception ?
>
> Thanks
> Daphna
>
> -----Original Message-----
> From: Jochen Wiedmann [mailto:jochen.wiedmann@gmail.com]
> Sent: Tuesday, October 27, 2009 8:32 PM
> To: xmlrpc-dev@ws.apache.org
> Subject: Re: Vague XML-RPC exceptions
>
> 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) <dw...@cisco.com> 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!
>
--
Germanys national anthem is the most boring in the world - how telling!
RE: Vague XML-RPC exceptions
Posted by "Daphna Wasserman (dwasserm)" <dw...@cisco.com>.
I understand its an SSL related problem, however I need information on the specific client which sent the bad message (there are dozens XML-RPC requests per minute). There is nothing in the XmlRpcErrorLogger which helps to identify that problematic client request. Can such information be added to the exception ?
Thanks
Daphna
-----Original Message-----
From: Jochen Wiedmann [mailto:jochen.wiedmann@gmail.com]
Sent: Tuesday, October 27, 2009 8:32 PM
To: xmlrpc-dev@ws.apache.org
Subject: Re: Vague XML-RPC exceptions
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) <dw...@cisco.com> 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!
Re: Vague XML-RPC exceptions
Posted by Jochen Wiedmann <jo...@gmail.com>.
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)
<dw...@cisco.com> 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!