In order to prevent some errant library code from setting an alarm

on one request and having it affect some later connection, force the
alarm to be cleared before each connection even if Apache's own
timeouts are being handled by the parent.  This doesn't help for multiple
requests on the same connection, but it is extremely unlikely that a
request stream would persist longer than a non-Apache errant timeout,
and this limits the problem to a single user without impacting performance.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@82583 13f79535-47bb-0310-9956-ffa450edef68