Re: SSL timeout while making XMLRPC call into roundup.

On Sat, Oct 27, 2012 at 1:50 PM, Ralf Schlatterbeck <[email protected]> wrote:
> On Sat, Oct 27, 2012 at 11:06:01AM -0400, Carlos O'Donell wrote:
>>
>> When the call takes more than 60 seconds to complete the server
>> sends back an SSL TLSv1 ALERT notifying us that the SSL connection
>> is going to close. This is bad since the XMLRPC command had not
>> yet returned a result.
>>
>> We are using roundup 1.4.8 with some significant modifications.
>> We are running roundup through mod_python i.e.
>>
>>  AddHandler python-program .py
>>  PythonHandler roundup.cgi.apache
>>
>> The Apache TimeOut is 300s, and KeelAliveTimeout shouldn't
>> apply because the connection was already initiated. We aren't
>> running roundup as a CGI client so the CGI client socket
>> timeouts don't apply.
>
> This is probably not a roundup issue, more likely apache or maybe a
> firewall setting. Do you have a firewall between the client and the
> server, maybe this is causing a timeout if nothing is sent for some
> time?

There is no firewall or proxy between the client and the server.
A firewall could not close the connection like this since it isn't
privy to the information in the encrypted channel and thus could
not issue the TLSv1 ALERT close_notify that precedes the socket
close.

There is only one relevant Apache2 timeout I know of e.g. TimeOut
which is set to 300 seconds, which is more than the timeout we're
seeing.

Is there any mod_python <-> roundup interaction that would limit
how long roundup can execute for? For example I know that PHP has
a maximum execution timeout for a script.

Cheers,
Carlos.

------------------------------------------------------------------------------
WINDOWS 8 is here. 
Millions of people.  Your app in 30 days.
Visit The Windows 8 Center at Sourceforge for all your go to resources.
http://windows8center.sourceforge.net/
join-generation-app-and-make-money-coding-fast/