Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Thread Crashing with Puma on 9.x #3673

Closed
TheKidCoder opened this issue Feb 16, 2016 · 2 comments
Closed

Thread Crashing with Puma on 9.x #3673

TheKidCoder opened this issue Feb 16, 2016 · 2 comments
Milestone
Invalid or Duplicate

Comments

@TheKidCoder
Copy link

I reported this on the puma/puma repo, but it probably belongs here.

I have a Rails 4.2.5.1 app running on Puma 2.16 on top of jRuby 1.7.23.
Everything works great there.

Everything else being the same, upgrading to jRuby 9.0.5.0 causes a strange issue.

Everything works fine, however, I will begin to see random thread exceptions (although more frequent the longer the app is running) when I use the rails send_data method.

Exception in thread "Ruby-0-Thread-44: /srv/www/reppro/shared/bundle/jruby/2.2.0/gems/puma-2.15.3-java/lib/puma/thread_pool.rb:61" IRReturnJump:<Static Type[1449297709]: local []:55>
Exception in thread "Ruby-0-Thread-54: /srv/www/reppro/shared/bundle/jruby/2.2.0/gems/puma-2.15.3-java/lib/puma/thread_pool.rb:61" IRReturnJump:<Static Type[594032292]: local []:55>

I would be more than happy to help triage this, just need some direction on what info you need.
@TheKidCoder TheKidCoder mentioned this issue Feb 16, 2016
Closed
@b1tfury
Copy link
Contributor

b1tfury commented Feb 27, 2016

@TheKidCoder Can you please share more information , maybe Puma.conf would be good.

@chrisseaton chrisseaton mentioned this issue Mar 7, 2016
Closed
@kares
Copy link
Member

kares commented Jan 17, 2017

return jumps were not handled properly until 9.1.3 (see #3713). please re-open if issue persist in latest 9.1

@kares kares closed this as completed Jan 17, 2017
@kares kares added this to the Invalid or Duplicate milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Invalid or Duplicate
Development

No branches or pull requests
3 participants
@kares @TheKidCoder @b1tfury