As indicated in the Configuring the Agent for Dynamics Environments section, setting the node name reuse flag causes the JVM to report graceful shutdowns, allowing the Controller to mark the corresponding node as historical. If you are not reusing node names, you can use one of these alternative methods to mark a node as historical:

• Set this system property at JVM startup:

  -Dappdynamics.jvm.shutdown.mark.node.as.historical=true

• Set this property in app-agent-config.xml to true:

  <app-agent-configuration>
  ...
  <configuration-properties>
  ...
  <property name="appdynamics.jvm.shutdown.mark.node.as.historical" value="true"/>

  Note: If your application environment abortively terminates JVMs rather than allowing them to shut down gracefully, arrange for your orchestration framework to use the controller API (Configuration API > Mark Nodes as Historical) to mark the node as historical at the same time as it terminates the node.