Memory Configuration

The  Tomcat bundle comes pre-configured with default memory usage settings. While the defaults are sufficient for initial usage, as your forms, business logic and submissions grow, so will the memory needs of the   server.

...

set JAVA_OPTS=-Xms128m -Xmx512m -Djava.awt.headless=true
-Dfrevvo.users.path="%CATALINA_HOME%\..\data\users"

Live Forms as a windows service

If you are running  as a Windows service, you will have to edit frevvo/tomcat/bin/service.bat line to increase the Java Heap and Permgen spaces. Here is an example of the line you need to edit in that file:

"%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-XX:MaxPermSize=128m 
-Djava.io.tmpdir=%CATALINA_BASE%\temp;
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager;
-Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties" 
--JvmMs 128 --JvmMx 512

See the documentation on Tomcat Windows Service for more details.

After making these modifications to the service.bat file, you must Remove/Reinstall Live Forms as a Windows service for the changes to take effect.

Insight Server Memory Settings

By default, the <frevvo-home>\solr-5.4.1\bin\solr script,sets the maximum Java heap size to 512M (-Xmx512m). This may not be sufficient especially when reporting on/indexing a large number of submissions. It may cause "out of memory" exceptions in the  <frevvo-home>solr-5.4.1\server\logs\solr.log file. The JVM heap size can be increased to resolve this. Make sure that the machine where the Insight Server is installed has enough memory to accommodate your changes.

...

To solve this edit setenv.[bat,sh] (or service.bat if you are running Live Forms as a Windows service) to increase the minimum and maximum heap size via the parameters: -Xmx and -Xms.

...

To solve this edit setenv.[bat,sh] (or service.bat if you are running Live Forms as a Windows service) to increase the maximum perm size via the paramenter: -XX:MaxPermSize

...