On Wednesday, February 8, 2017 at 3:02:12 AM UTC-8, Andy Shipman wrote: > > Thanks for the info on logging; that has been useful to get me a bit > further. > > At the moment, we see that the connection validator is working as > expected, but that itself times out in `__execute` > > Feb 07 19:55:50 app/web.1: I, [2017-02-07T19:55:49.690814 #25] INFO -- : > (0.015746s) (conn: 70034341617740) SELECT "ID", "TYPE", "LABEL", > "MANDATORY", "HIDDEN", "ORDER", "STATUS", "DEFAULT", "SAGE_KLASS", > "CREATED_AT", "UPDATED_AT", "COLUMN" FROM "FILTERS" ORDER BY "FILTERS"."ID" > Feb 07 21:54:45 app/web.1: I, [2017-02-07T21:54:44.581208 #25] INFO -- : > (943.562764s) (conn: 70034341617740) SELECT NULL FROM DUAL > > As you can see it is reusing the connection from pre-idle query, although > as far as we can tell we are seeing a new login in Oracle for that first > request after the idle period, so it _appears_ to be reconnecting in some > way? However all queries (post-idle period) even the simple "ping" for > connection validator still time out. >
The behavior you describe appears to indicate that ruby-oci8 reconnects internally. I looked through the documentation, and I cannot find a way to turn this off (or any mention of reconnection). There's not much Sequel can do in this case. I see you've already opened an issue in the ruby-oci8 repository, maybe they can provide more information. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
