New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConnectionPool#release not thread_safe #6464
Comments
It should be that easy. I think it's fixed on master, but please check. Regardless of whether or not this is fixed on master, please send a patch for 3-2-stable. :-) |
Looks like it's fixed on master. I'll have a pull request for 3-2-stable shortly. |
I faced this issue in my production application on Jruby 1.7.4 on Rails 3.2
|
You're using 3.2.8 of rails... This was fixed in a later patch release of rails 3.2 |
Thank you @aselder I will upgrade :) |
@tenderlove I am facing this issue again with following stacks: jRuby version: OS: JAVA version:
Rails version: Application Server |
I'm doing some pretty heavy concurrent use of ActiveRecord, and noticed so weird stack traces popping up in my logs
Is the fix as simple as wrapping the contents of the release method in a synchronize block?
The text was updated successfully, but these errors were encountered: