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... except in flask the connection is done at start up and so further db.blah() will not reconnect. Theoretically we have user/profiles in Oracle with no max idle time but they are (currently) read only. We are working on a minimalistic test case in case we actually want to suggest a patch (possibly in cx_Oracle or even flask itself), but I just thought I would throw the issue out there. It's my understanding that SQLA connection pooling is "supposed to" handle the issue of stale connections with a persistent app. But possibly I misinterpret. I did confirm with our DBA that we do NOT have connection pooling enabled at the Oracle level... and my guess is that this is correct if SQLA is handling the pooling... but I could be wrong here as well. Probably we can refactor the DB connection so that it pings before trying to connect, or otherwise disconnects after a user has done his business (or browser timeouts). At the moment I am not really sure if this should be implemented at our (flask) app level, with some flask hook, or with an SQLA hook (subclass of pooling method???)... or even if it's just a cx_Oracle driver issue. I believe, but am not 100% certain that this issue is very similar to the "mysql has gone away" thread that winds it's way through the internet. However, some basic attempts of using POOL_RECYCLE and try: db.doSomething() except: db.connect // again Have failed. But as I say, we have to make a minimal test case to demonstrate where the problem is. Thanks for you time, and interested to hear thoughts. Ben -- Ben Hitz Senior Scientific Programmer ** Saccharomyces Genome Database ** GO Consortium Stanford University ** h...@stanford.edu -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/wKO8vj6BSloJ. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
