Inactivity timeout not using defined timeout value.

[GoogleCodeExporter]

If a daemon process receives only a single request and after that the 
inactivity timeout would 
trigger, it potentially isn't triggering at the required time period.

The problem is that the inactivity timeout period isn't calculated into 
inactivity/deadlock checking 
loop until the first request arrives. As such, the need to consider the 
inactivity timeout isn't 
factored in until the first deadlock timeout period after that first request 
expires. If the remaining 
period in the deadlock timeout period at the time the first request arrives is 
greater than the 
inactivity timeout, then the inactivity timeout will not trigger until the 
longer deadlock timeout 
period has expired.

Original issue reported on code.google.com by Graham.Dumpleton@gmail.com on 4 Mar 2010 at 11:07

[GoogleCodeExporter]

Fixed in revision #1563 of trunk for mod_wsgi 4.0.

Original comment by Graham.Dumpleton@gmail.com on 2 Apr 2010 at 11:29

• Changed state: Started
• Added labels: Milestone-Release4.0

[GoogleCodeExporter]

Backport to mod_wsgi 3.X branch for 3.3 in revision 1600.

Original comment by Graham.Dumpleton@gmail.com on 12 Jul 2010 at 2:06

• Added labels: Milestone-Release3.3
• Removed labels: Milestone-Release4.0

[GoogleCodeExporter]

Version 3.3 has been released.

Original comment by Graham.Dumpleton@gmail.com on 31 Jul 2010 at 10:39

• Changed state: Fixed