On 8/2/07, Matthew K. Williams <[EMAIL PROTECTED]> wrote: > > I believe I've discovered an issue with > JdbcAdapterInternalService.begin() and JBoss' datasources -- JBoss is > closing the connection (active record isn't and is holding onto it to > boot!), then when the code attempts to start a transaction with a closed > connection, errors are thrown. > > I've followed the format of other methods such that if the connection is > stale, to request a new connection. It seems to be working thus far; > I've not seen errors as yet (other than the complaints about not having > closed connections and that the connection pool is closing them). > > I have tried setting ActiveRecord::Base.allow_concurrency = true, but it > didn't do much more than to cause the jvm hang and run out of memory. > > Long story short, I've attached the patch, if anyone is interested. > > I'm still curious about why the connections aren't getting closed > properly, but I'm entering day 4 of a migraine and I'm late on a > deadline, so I don't have the time/energy to commit to it I'd like. > Perhaps soon, but if anyone has any ideas, I'd like to hear them.
I'm afraid I don't have any ideas right now. The patch looks sufficiently general and useful that it might be a good candidate for inclusion -- we just need to consider whether auto-reconnect deep down at this point in the code is what we want, or should an exception be raised and/or should this be handled at a higher level. Thanks for continuing to look at this and digging up issues. Cheers, /Nick
_______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
