JRuby runtimes and database pool correlation

Hi,

I wanted to know whats the correlation between jruby runtimes that we
mention in warble.rb configuration file and the database pool that we
set in database.yml file. Is there any relation?

Is it that for each jruby runtime it creates the number of pool
mentioned in database.yml file?

or is it that pool mentioned in databse yml is not used in jruby?

We have used tomcat as app server if there is any relation with that
too. Version of tomcat is 6.0.26

Jruby 1.5.0
Rails 2.3.5

Any help would be really appreciated

On Dec 16, 2010, at 11:02 , Prachi T. wrote:

Hi,

I wanted to know whats the correlation between jruby runtimes that we
mention in warble.rb configuration file and the database pool that we
set in database.yml file. Is there any relation?

No, they are completely independent.

Is it that for each jruby runtime it creates the number of pool
mentioned in database.yml file?

or is it that pool mentioned in databse yml is not used in jruby?

The pool is used, there are two independent pools in use here; one for
the JRuby runtimes, and one in each runtime for the database
connections. Actually, it’s the case that if you have M JRuby runtimes
with a database pool size of N then you might actually check out M * N
connections if you can manage that much traffic/load.

Cheers,
/Nick