Re: [Sqlalchemy-tickets] [sqlalchemy] #2864: Disconnect via IDLE_TIME resource limit not handled by SQLAlchemy

[sqlalchemy <mi...@zz...>]

#2864: Disconnect via IDLE_TIME resource limit not handled by SQLAlchemy
----------------------------------+------------------------------------
      Reporter:  Bluehorn         |      Owner:  zzzeek
          Type:  defect           |     Status:  new
      Priority:  medium           |  Milestone:
     Component:  oracle           |   Severity:  no triage selected yet
    Resolution:                   |   Keywords:
Progress State:  awaiting triage  |
----------------------------------+------------------------------------

Comment (by Bluehorn):

 I forgot to mention how to configure the database server so that the
 connection is actually sniped. I used the following SQL commands (as
 sysdba) to restrict the example user loco_tl to one minute of idle time
 before being sniped. Note that Oracle does not check the expiration very
 often which means that I had to wait three minutes on average to have the
 connection really cut. I used attachment:list_sessions.sql to check when
 my connection was really sniped.


   `CREATE PROFILE short_idle LIMIT IDLE_TIME 1;`
   # see
 http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_6010.htm#SQLRF54200
   `ALTER USER loco_tl PROFILE short_idle;`
   # see
 http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_4003.htm
   `ALTER SYSTEM SET RESOURCE_LIMIT = TRUE;`
   # see
 http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm#i2198497

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2864#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python