I'm seeing an odd problem, where my MySQL connections never go away.
They're idle, but they just keep piling up (as reported by "mysqladmin
processlist") until I start getting errors about exceeding the maximum
number of allowed connections. Does this ring any bells with anyone? It
doesn't happen when running Django in "standalone development server"
mode, just with mod_python. Here's my setup:
Red Hat
Apache 2.0.52
Django from svn, revision 2558
using Eugene's #1442 patch, to store db connections in TLS
MySQL 5.0.18 (connecting via TCP, not a unix socket)
Python 2.4.2
mod_python 3.1.3
I'm using Apache's prefork MPM with 8 child processes, and every time I
hit a page, MySQL reports that a new, sleeping connection has been
created. I'd expect this for the first 8 requests, but what would cause
it to keep going up ad infinitum? If I "apachectl restart" then all the
connections go away again. And similarly, setting MaxRequestsPerChild
to a very low value (like 5) keeps things marginally under control, but
that's probably not a very good solution as far as performance goes of
course. I turned off DEBUG, but that didn't help. Any ideas?
p.s. kudos & thanks to the magic-removal team on the trunk merge. very
exciting!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
