For memory issues on Deep Security Manager (DSM), the Java Heap Memory Dump may be enabled to further investigate what is consuming the memory related to Deep Security Manager.exe or dsm_s (for Linux).
To Heap Dump threshold at 90% total heap memory usage, follow these steps:
- Switch to root on terminal or admin on cmd.
- Change path to the DSM installation directory.
- Run the following commands:
dsm_c -action changesetting -name settings.configuration.memoryManagerThresholdAutoHeapDump -value true
dsm_c -action changesetting -name settings.configuration.memoryManagerThreshold -value 0.9
The first command above will enable Java Heap Dump. The second command sets the threshold, 90% as shown in the example above. When the DSM process reaches 90% memory usage, it will generate Java Heap Dump.
To enable Heap Dump generation when manager is getting out of memory error, follow these steps:
- SSH to the target DSM Linux server and switch to root.
- Edit or create the dsm_s.vmoptions file.
# vi /opt/dsm/dsm_s.vmoptions
- Add a new line and enter this configuration.
- Below is an example what the content of the file looks like:
[firstname.lastname@example.org /]# cat /opt/dsm/dsm_s.vmoptions