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:  0.8.xx
     Component:  oracle    |   Severity:  trivial - <10 minutes
    Resolution:            |   Keywords:
Progress State:  in queue  |
---------------------------+-----------------------------------

Comment (by zzzeek):

 well the connection is "invalidated" when we detect disconnect but we
 don't assume that means "closed", for safety we run a "safe close", as
 you've noticed we don't propagate the exception there as we're expecting
 it to fail in many cases, this gets logged.   it's normal when an
 unexpected disconnect happens.   this could be improved if is_disconnect
 also gave out info regarding "try to close" or not, then we'd have to get
 that all into the pool logic and such, not sure if I'm eager to get into
 that as the pool's stability is pretty critical.

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