CODEWITHSUNDEEP
ruby-on-railsactiverecordruby-on-rails-3.1database-connectionconnection-timeout
Krista
Krista

Reputation: 915

ActiveRecord::ConnectionTimeoutError happening sporadically

Whenever I have an application using ActiveRecord I get this ConnectionTimeoutError - but always after a certain unknown period of time

ActiveRecord::ConnectionTimeoutError (could not obtain a database connection within 5 seconds.  The max pool size is currently 30; consider increasing it.):

It was previously set to 5, we have already increased it, and there is no way it can be using 30 connections at the same time. The only thing we use ActiveRecord for is our session store.

Our database.yml file looks like:

development:
  adapter: sqlite3
  database: db/development.sqlite3
  pool: 30
  timeout: 5000

(Test and production settings are the same)

I have been googling this occurrence, and just came across this posting:

https://groups.google.com/forum/#!msg/copenhagen-ruby-user-group/GEHgi_WudmM/gnCiwWqmVfMJ

Which mentions that ActiveRecord does not check a connection back into the pool once it is done with it?? Is that true? Do I need to manually manage the connections?

I appreciate any advice!!

edit I should probably mention I am running Rails 3.1.3

Upvotes: 24

Views: 15928

Answers (4)

TheGrassIsAlwaysMondegreen
TheGrassIsAlwaysMondegreen

Reputation: 21

I was also experiencing a similar problem with a Sinatra App, I added 

after do
  ActiveRecord::Base.clear_active_connections!
end

To my application controller and it solved my problem.

This construct is known as a filter and it evaluates after each request.

I'm not sure what was actually happening with the application, but I would suspect that connections weren't being closed after each request.

Upvotes: 2

Ronak Jain
Ronak Jain

Reputation: 1783

Applies also to Rails 5, since Puma is default server.

If you are using Threaded Servers like Puma, Phushion Passenger, they create multiple threads of the same application. Thereby making your application run faster, by concurrently executing each incoming requests.

Make sure that the pool size is equal or more than the number of threads. I was having an issue when few of my threads were giving me ActiveRecord::ConnectionTimeoutError, and the problem was vague since it occurs once in a while not very often.

Upvotes: 2

user3632955
user3632955

Reputation: 45

I used this code on my Sinatra app

after do
  ActiveRecord::Base.clear_active_connections!
end

This solve my problem

Upvotes: 2

Kyle C
Kyle C

Reputation: 4097

Rails has a middleware called ActiveRecord::ConnectionAdapters::ConnectionManagement which clears active connections every request so they do not stick around. Check your middleware to make sure you have this (which is there by default), run "rake middleware". You should not have to manage the connections manually to answer your last question.

Run this in your console

   ActiveRecord::Base.clear_active_connections!

Upvotes: 15

Related Questions