You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2009/09/18 19:58:08 UTC

DO NOT REPLY [Bug 47873] New: unreliable coordination between daemon and request thread for BusyTimeout processing

https://issues.apache.org/bugzilla/show_bug.cgi?id=47873

           Summary: unreliable coordination between daemon and request
                    thread for BusyTimeout processing
           Product: Apache httpd-2
           Version: 2.3-HEAD
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_fcgid
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: trawick@apache.org


See references to busy_timeout in fcgid_bridge.c (request thread) and
fcgid_pm_main.c (daemon) for the implementation of BusyTimeout processing.

Currently, the two threads need to agree on whether or not the app will be
timed out, or both may release the corresponding procnode structure.  A fudge
factor (10 seconds) is added to the BusyTimeout setting in the daemon when
checking for a timeout, presumably to reduce the likelihood that the timeout is
processed (i.e., the daemon releases the procnode structure) but the request
thread doesn't think so (i.e., the request thread also releases the procnode
structure).

Note that this implementation also requires the busy_timeout value to be
propagated from the main server conf to the virtual host conf in fcgid_conf.c. 
Hopefully that propagation can be removed when this is resolved.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 47873] unreliable coordination between daemon and request thread for BusyTimeout processing

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=47873

Ryan Pan <pq...@mailtech.cn> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 47873] unreliable coordination between daemon and request thread for BusyTimeout processing

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=47873

Jeff Trawick <tr...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #1 from Jeff Trawick <tr...@apache.org> 2009-12-15 06:55:48 UTC ---
Regarding the comment "this implementation also requires the busy_timeout value
to be propagated from the main server conf to the virtual host conf in
fcgid_conf.c":

That was true at one time -- when FcgidBusyTimeout couldn't be set inside a
vhost.  Once that restriction was removed, there was no unnatural propagation
of the busy_timeout value.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org