OutOfMemory: Java Heap Space in CSR server.log
The following error is recorded in the Server Error log (...\Content Security Reporter\reporter\log\server.log):
2012-06-14 16:32:30,909 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap space
This error indicates that Content Security Reporter was unable to extend the Java heap space needed to perform some task. Typically this error causes some part of the Content Security Reporter service to fail and requires a service restart.
Under most circumstances, the default of 1024 MB for Java memory is sufficient, so it is important to learn what caused the error. Increasing the memory without addressing the issue can simply delay the issue, but not fix it. Increasing the memory to arbitrarily large values can actually decrease performance over time.
How to Fix
Increase the amount of Java Virtual Machine memory available to Content Security Reporter server using the following instructions:
- Log on to the ePO™ console.
- Change the memory allocation under Menu > Configuration > Report Server Settings > Performance Options and click OK. For 32-bit installations the memory must be between 1024 MB and 1536 MB.
NOTE: This change affects the Content Security Reporter server, which might be different from the ePO server.
- Restart the Content Security Reporter service for the new memory settings to take effect. In Windows > Start > Run, type services.msc, and restart the service Skyhigh Content Security Reporter.
If the memory setting is too large, the Content Security Reporter service will not start. You can resolve the issue by deleting or modifying the memoryalloc.conf file manually. The memoryalloc.conf file exists only if you changed the memory value using the ePO console or if you created the file manually.
.../Content Security Reporter/reporter/conf/memoryalloc.conf
Example entry in the memoryalloc.conf file: max_memory_allocation=1024