DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=23548>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=23548 prefork model on solaris 2.6 mod_ldap leaves connections to ldap in close_wait ------- Additional Comments From [EMAIL PROTECTED] 2004-05-21 16:16 ------- As I understand it, the Shared Connection Pool is on by default. You bring up a good point though. Maybe it's a matter of adjusting this shared pool inside the source code. I don't see anyway to do that from a config line. The documentation simply says it's on by default. It's still curious that we only see this under solaris 2.6 (and perhaps another person sees it under redhat). Although I can see how this could simply be a mask of the problem perhaps (we see it earlier on 2.6 and our 2.8 environments doesn't get similar traffic patterns?). Anyway... THANKS! I will look into the code from this angle, sometimes it just takes another pair of eyes. LDAP Connection Pool LDAP connections are pooled from request to request. This allows the LDAP server to remain connected and bound ready for the next request, without the need to unbind/connect/rebind. The performance advantages are similar to the effect of HTTP keepalives. On a busy server it is possible that many requests will try and access the same LDAP server connection simultaneously. Where an LDAP connection is in use, Apache will create a new connection alongside the original one. This ensures that the connection pool does not become a bottleneck. There is no need to manually enable connection pooling in the Apache configuration. Any module using this module for access to LDAP services will share the connection pool. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
