You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to shut down the Agent cleanly without exiting the host JVM. This could be useful in one-off troubleshooting cases where the Agent functionality is only desired for a relatively short period of time, or in case the Agent causes some disruption to the host application JVM.
The first most obvious way to do this would be to use the existing SignalHandler to catch some user-configurable signal that the OpenJDK JVM does not already respond to by default. It could also be done by an authenticated WebServer request. In any case, the event should initiate an orderly shutdown of the Agent's webserver, harvester, and any other threads.
The text was updated successfully, but these errors were encountered:
Related #233
It should be possible to shut down the Agent cleanly without exiting the host JVM. This could be useful in one-off troubleshooting cases where the Agent functionality is only desired for a relatively short period of time, or in case the Agent causes some disruption to the host application JVM.
The first most obvious way to do this would be to use the existing SignalHandler to catch some user-configurable signal that the OpenJDK JVM does not already respond to by default. It could also be done by an authenticated WebServer request. In any case, the event should initiate an orderly shutdown of the Agent's webserver, harvester, and any other threads.
The text was updated successfully, but these errors were encountered: