-
Notifications
You must be signed in to change notification settings - Fork 17
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
Monitoring loop exits prematurely #42
Comments
I'll reopen this issue and revert the changes, because JoularJX agent is running continuously even after the program ends. |
Makes sense. Sorry for the issue. |
@metacosm, do you have any additional insights about this issue? |
I haven't looked into it, to be honest. I don't have any idea off the top of my head to address the issue in both cases. |
Thanks, I'll close the issue for now, and if anything new comes by, I'll reopen it. |
The issue comes from the fact that the
DestroyJavaVM
Thread is actually present before the VM is scheduled to be destroyed in a lot of contexts (in particular, for daemon-like processes) where the VM isn't actually shutting down.The text was updated successfully, but these errors were encountered: