Forums » Rails-core » MySQL doesnt close connections

Trying to track it down now, but I svn up'd right after running 
successful
tests, and running the tests again runs until mysql reaches its 
connection
limit and all further tests fail with too many connections errors. I've
verified that the connections aren't getting closed with mysqladmin
processlist. I'll toss up a patch if I can figure it out, I think it has
something to do with changeset ( 
http://dev.rubyonrails.org/changeset/3693
). Can someone else verify this please?



Bob Silva

http://www.railtie.net/

Still haven't tracked it down, but if I set @@allow_concurrency = true, 
the
test suite passes fine.



Bob Silva

http://www.railtie.net/

  _____

From: rails-core-bounces@lists.rubyonrails.org
[mailto:rails-core-bounces@lists.rubyonrails.org] On Behalf Of Bob Silva
Sent: Wednesday, March 01, 2006 11:47 PM
To: rails-core@lists.rubyonrails.org
Subject: [Rails-core] MySQL doesnt close connections



Trying to track it down now, but I svn up'd right after running 
successful
tests, and running the tests again runs until mysql reaches its 
connection
limit and all further tests fail with too many connections errors. I've
verified that the connections aren't getting closed with mysqladmin
processlist. I'll toss up a patch if I can figure it out, I think it has
something to do with changeset ( 
http://dev.rubyonrails.org/changeset/3693
). Can someone else verify this please?



Bob Silva

http://www.railtie.net/

Bob Silva wrote:
> Trying to track it down now, but I svn up'd right after running successful
> tests, and running the tests again runs until mysql reaches its connection
> limit and all further tests fail with too many connections errors. I've
> verified that the connections aren't getting closed with mysqladmin
> processlist. I'll toss up a patch if I can figure it out, I think it has
> something to do with changeset ( http://dev.rubyonrails.org/changeset/3693
> ). Can someone else verify this please?
>
>  
Changeset 3693 is broken in several ways. I'm in the process of fixing 
it.

-- stefan

--
For rails performance tuning, see: http://railsexpress.de/blog
Subscription: http://railsexpress.de/blog/xml/rss20/feed.xml

Bob Silva wrote:
> Still haven't tracked it down, but if I set @@allow_concurrency = true, the
> test suite passes fine.
>   
No one has ever run the tests with allow_concurrency = false, because
the default was allow_concurrency = true. Maybe the test system probably
was never fit for this scenario.

I suspect their is no problem for actual applications, after applying
http://dev.rubyonrails.org/ticket/4044, that is.

At least I don't have a problem running 8000 requests against my app,
with allow_concurrency = false

I'll leave it to the testing gurus to resolve this problem.

-- stefan

--
For rails performance tuning, see: http://railsexpress.de/blog
Subscription: http://railsexpress.de/blog/xml/rss20/feed.xml