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
Provide at least:
JRuby and puma (version 4.2.1) lib should receive another connection.
Puma not accept another request because it's deadlock on child process. See more detail here puma/puma#1744
I recommended to upgrade ruby from 2.5.3 to 2.5.7 ASAP.
thanks
The text was updated successfully, but these errors were encountered:
I have already confirm this issue by remove puma from my project and using WEBrick (1.4.2) instead, it's worked.
Sorry, something went wrong.
@mrnonz would it be possible for you to come up with a reproducer?
also I do not understand what you mean by:
Fixed by #5917
hey @mrnonz, still a bit confused what exactly from the stdlib 2.5.5 upgrade caused the Puma issue. only found an issue w worker mode (MRI 2.5.5 had a Process.fork fix) which isn't supported on JRuby
Process.fork
No branches or pull requests
Environment
Provide at least:
Expected Behavior
JRuby and puma (version 4.2.1) lib should receive another connection.
Actual Behavior
Puma not accept another request because it's deadlock on child process. See more detail here puma/puma#1744
I recommended to upgrade ruby from 2.5.3 to 2.5.7 ASAP.
thanks
The text was updated successfully, but these errors were encountered: