-
Notifications
You must be signed in to change notification settings - Fork 327
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
No way to fully shut down Kamon 1.0 #502
Comments
hello @ruippeixotog, thanks for reporting this! We will take a look it asap :) |
oh yes, that's a show stopper for us. Since adding the Kamon dependency, there are more and more situations in which our application is not able to shutdown correctly. This is even more a problem because this is our way to reload the application if the configuration in Consul changes... application exits and is restarted by docker. Now the application tries to stop but keeps hanging in an undefined state. |
There should be a way to completely shut down Kamon programatically, making the JVM terminate normally without recurring to explicit
System.exit
calls. With Kamon 1.0, unfortunately, I can't seem to do this:It seems that due to the
registryExecutionContext
insideReporterRegistry
, the JVM keeps active threads that prevent the JVM shutdown. We should be able to shut down theregistryExecutionContext
either by aKamon.stop()
method like before or bystopAllReporters()
.The text was updated successfully, but these errors were encountered: