some situations that may be screwing up the connection pool like this include (and are not limited to):
* your application may not be properly closing, resetting or returning a connection when there is an exception; * multiple threads/processes are using the same connection because of how it was obtained/shared/returned when dealing with this stuff in pyramid and twisted, i did a lot of debug logging in Python and the Database where I was just concerned with looking at the ids of a thread/process and the db connection at certain points in the code /and/ when the exception was raised. doing that you can usually look backwards in the logs from the exception and see where that database connection was obtained and what it's history was. with django, i'd pay attention to the request start, request end, and whenever there is an exception. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/a6d1e056-964a-4ac1-a224-c05a9dab05b8%40googlegroups.com.
