Restart the Connectivity Agent

You can restart the on-premises connectivity agent if required.

Stop the agent in either of the following ways:
- Enter ctrl+c on the host on which the agent is running.
- Search for the connectivity agent process and terminate it.
Wait at least 45 seconds before restarting the agent. This is because the agent monitoring framework waits for 45 seconds before marking the agent status as being down. If you start the agent before 45 seconds have completed, agent restart fails with the following error message:
```
Agent is already running for this particular instance
```

Restart the agent based on your environment and production load size.

Environment Enter the Following Command

Production environments

Environment	Enter the Following Command
Production environments	It is recommended that you restart the agent with the `-XX:+HeapDumpOnOutOfMemoryError` parameter: `java -XX:+HeapDumpOnOutOfMemoryError -jar connectivityagent.jar` If the connectivity agent runs out of memory, this parameter by default ensures that the heap dump is stored in a `java_pidpid.hprof` file in the directory where the agent application is run. Based on production loads, it may sometimes be necessary to allocate a larger amount of heap size for the agent process. If you determine that the process must be allocated a larger heap size, tune the `-Xms` and `-Xmx` parameters accordingly. `-Xmsheap_sizeG` `-Xmxheap_sizeG` For example, assume you want to assign a minimum of 2 GB and a maximum of 8 GB to the agent JVM. `-Xms2G -Xmx8G` Start the agent with the following parameters. `java -Xms2G -Xmx8G -jar connectivityagent.jar` You can specify the `-XX`, `-Xms`, and `-Xmx` parameters at the same time, if needed.
Nonproduction environments	`java –jar connectivityagent.jar`

It is recommended that you restart the agent with the -XX:+HeapDumpOnOutOfMemoryError parameter:

java -XX:+HeapDumpOnOutOfMemoryError -jar connectivityagent.jar

If the connectivity agent runs out of memory, this parameter by default ensures that the heap dump is stored in a java_pidpid.hprof file in the directory where the agent application is run.

Based on production loads, it may sometimes be necessary to allocate a larger amount of heap size for the agent process. If you determine that the process must be allocated a larger heap size, tune the -Xms and -Xmx parameters accordingly.

-Xmsheap_sizeG
-Xmxheap_sizeG

For example, assume you want to assign a minimum of 2 GB and a maximum of 8 GB to the agent JVM.

-Xms2G -Xmx8G

Start the agent with the following parameters.

java -Xms2G -Xmx8G -jar connectivityagent.jar

You can specify the -XX, -Xms, and -Xmx parameters at the same time, if needed.

Nonproduction environments

java –jar connectivityagent.jar

You can restart the agent as a background process. See Run the Connectivity Agent as a Service.