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 2011/04/26 09:57:25 UTC

DO NOT REPLY [Bug 51118] New: LDAP cache is cleared after graceful/restart and ongoing client processes can't access the newly created cache

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

           Summary: LDAP cache is cleared after graceful/restart and
                    ongoing client processes can't access the newly
                    created cache
           Product: Apache httpd-2
           Version: 2.2.17
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_ldap
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: siukola.antti@gmail.com


LDAP cache is cleared after graceful/restart and ongoing client connections
can't access the newly created cache. This causes client connections to last
very long especially with DAV connections when path authorisation is being used
(ldap searches/cache hits can be up to thousands per client action).

1. Cache should be accessible by already ongoing client connections

2. Option to not clear the cache on graceful/restart

-- 
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 51118] LDAP cache is cleared after graceful/restart and ongoing client processes can't access the newly created cache

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

--- Comment #1 from Eric Covener <co...@gmail.com> 2011-04-27 12:37:10 EDT ---
Another idea would be a non-default option to let the child create a local
cache, which users would opt-in to if they had ldap protected requests with
thousands of subrequests (if I understand the report/issue correctly).  Perhaps
The child would only use it when it was exiting _and_ had some hint that it was
chugging through subrequests.

-- 
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