This section gives some initial guidance on configuring the JVM for running OpenAM. These settings provide a strong foundation to the JVM before a more detailed garbage collection tuning exercise, or as best practice configuration for production.
Table 18.6. Heap Size Settings
| JVM Parameters | Suggested Value | Description |
|---|---|---|
|
|
At least 1024m (2048m with embedded OpenDJ), in production environments at least 2048m to 3072m. This setting depends on the available physical memory, and on whether a 32 or 64-bit JVM is used. |
- |
|
|
- |
Ensures the server JVM is used |
|
|
Set both to 256m |
Controls the size of the permanent generation 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. |
Table 18.7. Garbage Collection Settings
| JVM Parameters | Suggested Value | Description |
|---|---|---|
|
|
- |
Verbose garbage collection reporting |
|
|
|
Location of the verbose garbage collection log file |
|
|
- |
Prints a heap histogram when a SIGTERM signal is received by the JVM |
|
|
- |
Prints detailed information about garbage collection |
|
|
- |
Prints detailed garbage collection timings |
|
|
- |
Out of Memory errors generate a heap dump automatically |
|
|
|
Location of the heap dump |
|
|
- |
Use the concurrent mark sweep garbage collector |
|
|
- |
Aggressive compaction at full collection |
|
|
- |
Allow class unloading during CMS sweeps |
