From: Eric Covener <covener@apache.org>
Date: Tue, 5 Mar 2013 15:55:17 +0000 (+0000)
Subject: for now, mention that the TTL isn't tracking to the last I/O on the LDAP conn.
X-Git-Tag: 2.5.0-alpha~5700
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6a74a78f2b0563423b0f480d2a5fdc7bd1269c1a;p=apache

for now, mention that the TTL isn't tracking to the last I/O on the LDAP conn.



git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1452865 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_ldap.xml b/docs/manual/mod/mod_ldap.xml
index 09af632420..bbc9f2db55 100644
--- a/docs/manual/mod/mod_ldap.xml
+++ b/docs/manual/mod/mod_ldap.xml
@@ -736,6 +736,11 @@ connection client certificates.</description>
     connection pool.  The default value of -1, and any other negative value,
      allows connections of any age to be reused.</p>
 
+    <p>The timemout is based on when the LDAP connection is returned to the 
+    pool, not based on the last time I/O has been performed over the backend
+    connection.  If the information is cached, the apparent idle time can exceed
+    the <directive>LDAPConnectionPoolTTL</directive>. </p> 
+
     <note><p>This timeout defaults to units of seconds, but accepts
     suffixes for milliseconds (ms), minutes (min), and hours (h).
     </p></note>