hm, i'm looking at the ext source ( https://github.com/bbangert/beaker/blob/master/beaker/ext/database.py ) and the files mike noted as well.
i likely missed something, but I don't see anything in the ext.backend or pyramid_beaker that handles closing connections, and it looks like very rudimentary connection/pooling management just a couple ideas , likely bad ones : how many requests /connections do you need to re-create this ? could you try using a query log that shows the connection id ? that helps me bugfix most sql and framework issues could you try a dirty hack, save the session connection to a request (or other) attribute, and then use a subscriber to manually close it ? is there anything in the connection string that is overlapping with your app ? any chance sqlalchemy is keeping the app open because it thinks it's the session ? -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
