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
Puma does not shutdown gracefully #1675
Comments
Issue not with Puma. Opened a issue in suckerpunch. |
I did some debugging and found out that This can be observed by adding a
|
Should be fixed by jruby/jruby#5441 |
Ignore my previous comments, the following code is the easiest way to reproduce this issue
This issue can be replicated in the above code using JRuby. I tried debugging a little bit and will update this issue if I can find the root cause. I tried using a |
@Adithya-copart what version of Puma are you using? |
@dentarg Here is my
|
Sample app without suckerpunch. |
Using
Ctrl + C
orpumactl stop
does not shutdown puma gracefully.Gemfile:
Gemfile.lock:
test_app.rb:
config.ru
Steps to reproduce
bundle install
and thenbundle exec puma
.Hit the URL
get '/'
to trigger the jobs.Use
Ctrl + C
orpumactl stop
.Expected behavior
Puma should shutdown gracefully.
Actual behavior
Puma doesn't shutdown gracefully and prints the following every time
Ctrl + C
orpumactl stop -p <pid>
is used:The following is the first two lines after
Ctrl + \
However, graceful shutdown is successful when:
get '/'
is not opened.get '/pry'
is opened followed byget '/'
.The results when using
bundler/inline
are different and the shutdown is successful.test_app_bundler_inline:
System configuration
Ruby version:
jruby 9.2.0.0 (2.5.0) 2018-05-24 81156a8 Java HotSpot(TM) 64-Bit Server VM 25.181-b13 on 1.8.0_181-b13 +jit [darwin-x86_64]
Rails version: NA
Puma version:
puma (3.12.0-java)
EDIT: Removed the reference to #1382 as it deals with workers in clustered mode.
The text was updated successfully, but these errors were encountered: