On Oct 17, 2012, at 3:48 PM, Ben Hitz wrote:
>
> Oh thanks, I hadn't dug that deeply into FSQLA yet.This is narrowing down
> the issue though. Our anecdotal experience is that pool_recycle is not doing
> anything with Oracle... hopefully have a test (or ideally a "never mind")
> follow u
that's not entirely accurate. The Flask-SQLAlchemy extension checks out a
connection from the connection pool at request start, returns it at request
end. The pool is responsible for dealing with the lifecycle of database
connections and can be confiugured to deal with this. To deal with
co
On Oct 16, 2012, at 5:56 PM, Ben Hitz wrote:
> Has anyone ever tested the pool_recycle in Oracle when a user has a maximum
> idle time? We are having an issue with a flask/sqla/cx_oracle stack where
> when the DB_USERs idle time expires, Oracle throws us:
>
> ORA-02396: exceeded maximum idle
Has anyone ever tested the pool_recycle in Oracle when a user has a maximum
idle time? We are having an issue with a flask/sqla/cx_oracle stack where
when the DB_USERs idle time expires, Oracle throws us:
ORA-02396: exceeded maximum idle time, please connect again. Which is no
big deal... ex
