Tune JVM settings
This section gives some initial guidance on configuring the JVM for running AM when the deployment has a dedicated CTS token store, and AM is configured to use server-side sessions.
These settings provide a strong foundation to the JVM before a more detailed garbage collection tuning exercise, or as best practice configuration for production:
| JVM parameters | Suggested value | Description | 
|---|---|---|
| 
 | At least 1 GB (2 GB with embedded DS), in production environments at least 2 GB to 3 GB. This setting depends on the available physical memory, and on whether a 32- or 64-bit JVM is used. | |
| 
 | Set both to 256 MB | Controls the size of the metaspace in the JVM | 
| 
 | 60000 | Controls the read timeout in the Java HTTP client implementation. This applies only to the Sun/Oracle HotSpot JVM. | 
| 
 | High setting: 30000 (30 seconds) | Controls the connect timeout in the Java HTTP client implementation When you have hundreds of incoming requests per second, reduce this value to avoid a huge connection queue. This applies only to the Sun/Oracle HotSpot JVM. | 
| JVM parameters | Suggested value | Description | 
|---|---|---|
| 
 | 
 | Controls the protocols used for outbound HTTPS connections from AM. Specify one or more of the following values, separated by commas: 
 This setting applies only to Sun/Oracle Java environments. | 
| 
 | 
 | Controls the protocol AM uses to connect to affected external resources. Specify one or more of the following values, separated by commas: 
 This setting overrides the default server value. For details, refer to advanced properties. | 
| JVM parameters | Suggested value | Description | 
|---|---|---|
| 
 | Verbose garbage collection reporting. | |
| 
 | 
 | Logs detailed information about garbage collection.
When using the  | 
| 
 | Out of Memory errors generate a heap dump automatically. | |
| 
 | 
 | Location of the heap dump. | 
| 
 | Prints a heap histogram when the JVM receives a SIGTERM signal. |