I have read Arun G.'s
on using jruby/rails with a glassfish database connection pool and I
been able to set this up. I have a question regarding this though that
sure someone has encountered. Doesn’t rails use persistent connections,
which would prevent them from being returned to the pool?
I am concerned (and some simple tests seem to bear this out) that
a deployment that handles multiple simultaneous users will saturate the
connection pool and some of the threads will never get a connection.
If this is the case, can I configure rails to not use persistent
connections, or can I use an idle timeout setting on glassfish to