This generally happens because of an issue in your exception handling or because you are trying to share a database connection across process boundaries.
The first thing to do is to check if you are connecting to the database before gunicorn forked. If so, this will likely go away if you call `dispose` on the SqlAlchemy engine. `dispose` will essentially reset the connection pool, and ensure each worker will have it's own, dedicated pool There could also be an issue where you are sharing a Session across requests or process boundaries. that can be harder to pinpoint. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/7cc14061-1c9f-4980-b5eb-722c723240f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
