On 11/2/07, Atilla <[EMAIL PROTECTED]> wrote: > If the DB connection pool has low usage and ends up with a number of > transactions that are not active for a while - they will expire and > this error will be thrown.
That's why you set connection_timeout to a significantly lower value than the server has. I use 1 hour on the client and 24 hours on the server. Even 1/2 hour on the client should cause no noticeable overhead. Your original problem was your engine options weren't being passed to SQLAlchemy, thus the timeout. So theoretically you've solved it. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
