Fixing Out of Memory Issues

If you encounter java.lang.OutOfMemoryError for a process in the log, the CloudView memory setting may be too low. You can increase memory allocation for any CloudView process in <INSTALLDIR>\<OS>\cv\data\config\DeploymentInternal.xml. CloudView processes are C++ and Java-based. The C++ part consumes most of the memory. Changing memory setting as explained below does not impact memory allocation in the C++ part.

This task shows you how to:

Solve java.lang.OutOfMemoryError: Java heap space
Solve java.lang.OutOfMemoryError: PermGen space

Solve java.lang.OutOfMemoryError: Java heap space

This issue is solved by increasing the maximum heap size (-Xmx parameter).

Go to <DATADIR>/config.
Edit DeploymentInternal.xml and look for the process in which the issue occurred:
- searchserver
- indexingserver
- consolidationserver
- java (for all processes)
Increase -Xmx by 50%.
To rebuild the configuration:
1. Go to <INSTALLDIR>\<OS>\cv\data\bin
2. Run the following command:
```
./buildgct
```
The following message displays: Configuration built successfully

To check the changes on Windows, run the following command:

WMIC /OUTPUT:C:\ProcessList.txt PROCESS get Caption,Commandline,Processid

Solve java.lang.OutOfMemoryError: PermGen space

This issue is solved by specifying the size of permanent generation (-XX:MaxPermSize parameter).

Go to <DATADIR>/config.
Edit DeploymentInternal.xml and look for the process in which the issue occurred:
- searchserver
- indexingserver
- consolidationserver
- java (for all processes)
Increase -XX:MaxPermSize by 50%.
To rebuild the configuration:
1. Go to <INSTALLDIR>\<OS>\cv\data\bin
2. Run the following command:
```
./buildgct
```
The following message displays: Configuration built successfully

To check the changes on Windows, run the following command:

WMIC /OUTPUT:C:\ProcessList.txt PROCESS get Caption,Commandline,Processid