-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Native threads are nil #11450
Comments
Thanks for the report, during shutdown threads eventually die (and get garbage collected). |
sorry for the confusion - seems this has been happening on start (before shutdown trigger). |
necessary since native (Java) thread is kept as a weak ref so un-wrapping should deal with a potentially GCd instance resolves elasticGH-11450
necessary since native (Java) thread is kept as a weak ref so un-wrapping should deal with a potentially GCd instance resolves elasticGH-11450
necessary since native (Java) thread is kept as a weak ref so un-wrapping should deal with a potentially GCd instance resolves elasticGH-11450
Please post all product and debugging questions on our forum. Your questions will reach our wider community members there, and if we confirm that there is a bug, then we can open a new issue here.
For security vulnerabilities please only send reports to security@elastic.co.
See https://www.elastic.co/community/security for more information.
Logstash Plugins are located in a different organization: https://github.com/logstash-plugins. For bugs on specific Logstash plugins, for example, if Redis Output has a defect, please open it in the respective Redis Output repository.
For all general issues, please provide the following details for fast resolution:
Issue:
It seems the native threads are nil. I don't know what could cause this. Any suggestions?
The text was updated successfully, but these errors were encountered: