SSL timeout while making XMLRPC call into roundup.

Roundup Users,

I have a somewhat long running XMLRPC call that runs within
roundup and that call takes more than 60 seconds to complete,
at which point the server closes the socket and that causes
the XMLRPC command to fail since no result was returned.

Has anyone run into this before?

At first I thought this was a client-side timeout and I tried
increasing all of the timeout values on the client side, but 
after more detailed analysis for the client<->server traffic
we found that it was the server closing the socket.

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.

We've been pouring over the documentation and trying 
this-and-that, but I figured perhaps someone on the roundup 
list might have run into this before with a configuration
closer to what we have.

What could be timing out on the server?

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/