Red Hat Bugzilla – Bug 293171
Default timeout causes connection timeouts against busy servers
Last modified: 2007-11-30 17:07:47 EST
+++ This bug was initially created as a clone of Bug #250300 +++
Description of problem:
The addition of the default timeout of 30 seconds causes connection timeouts
against busy servers or those with many registered clients.
Version-Release number of selected component (if applicable):
Always against busy servers.
Steps to Reproduce:
1. Create secure server with
# rhnreg_ks --activationkey=test-activation-key
Connection timed out on readline
The issue is with the DEFAULT_TIMEOUT in
/usr/lib/python2.4/site-packages/rhn/SSL.py and its use in connections.py.
Whilst a timeout of 30 seconds might not be unreasonable for the SSL connection
to take place it is not suitable for the ongoing connection. The socket timeout
should be reset to a more reasonable value once the SSL connection is in place.
Attached is a server-side cgi which just delays for a requested amount of time
and a small python script to exercise this cgi via the rhnlib code.
-- Additional comment from firstname.lastname@example.org on 2007-07-31 13:43 EST --
Created an attachment (id=160345)
python test example
-- Additional comment from email@example.com on 2007-07-31 13:45 EST --
Created an attachment (id=160346)
server-side delay routine
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update