It sounds like you just aren't closing the connections when you're done with them. The request callbacks provide a way to deal with this if you can't just immediately close the connection.
On Thu, Dec 29, 2011 at 10:29 AM, Stephan Ellis <stephan.el...@gmail.com>wrote: > Hello All, > > I'm looking for some guidance. I wrote a small app that uses > python-ldap to query and modify a Directory (MS Active Directory). The > problem I'm having is that occasionally the AD server stops accepting new > connections and netstat shows a ton of connections to the directory > server. What I'm wondering is, what is the best way to create a connection > or pool of connections and then have each request reuse that connection. > > I also found this: > > http://pypi.python.org/pypi/ldappool/ > > which looks like it can handle the pool of connections for me, but I'm not > sure where I should create the pool in my app so that the views can exploit > it. > > Thanks in advance! > > -stephan > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to pylons-discuss@googlegroups.com. > To unsubscribe from this group, send email to > pylons-discuss+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
