Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Subject: DO NOT REPLY [Bug 47634] mod_ldap connection pool session keepalive
 not implemented
In-Reply-To: <bug-47634-7868@https.issues.apache.org/bugzilla/>
References: <bug-47634-7868@https.issues.apache.org/bugzilla/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-Id: <20100112235507.D9199234C1EE@brutus.apache.org>
Date: Tue, 12 Jan 2010 15:55:07 -0800 (PST)

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

--- Comment #7 from Stefan Fritsch <sf@sfritsch.de> 2010-01-12 15:55:04 UTC ---
(In reply to comment #5)
> Other options:
> - implement some sort of "check" logic when a connection is requested from the
> pool. If it doesn't return in a reasonable amount of time (re-use the
> connection time out time or add another parameter) then unbind the connection
> and rebind

Something like this is now implemented in trunk in r898102: There is a new
timeout value for search/bind. If the timeout is reached, the operation is
retried after unbind/rebind (at least for the initial bind after an old
connection is taken from the pool).

Note that at least with openldap, you can influence mod_ldap with
/etc/ldap.conf and $HOME/.ldaprc (especially with the TIMEOUT parameter). Httpd
2.2.x will return 500 if TIMEOUT triggers, but this may still be better than
the child waiting for > 15 minutes.

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