On Tuesday, January 6, 2015 11:05:58 AM UTC-8, Lin Jen-Shin wrote: > > Umm... I just checked the trace for sequel, and I am not sure why it's the > case. > The disconnection happened on: > sequel-4.18.0/lib/sequel/connection_pool/threaded.rb:88 > > def hold(server=nil) > t = Thread.current > if conn = owned_connection(t) > return yield(conn) > end > begin > => unless conn = acquire(t) > > I thought since I already have the middleware doing DB.synchronize, > the underlying query should simply get the connection from > `owned_connection(t)`? We do have threads making queries, but > I think in this case it should be the same thread doing DB.synchronize. >
It is true if that if you are doing DB.synchronize in a rack middleware, you should not reaching the acquire call inside the application (unless you are spawning threads inside the request). But it's hard to tell what the issue is without a full backtrace. 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 http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
