...

The first important step is to ensure that  is installed on a machine with sufficient cpu and ram. "Sufficient" depends on your  usage (number of users, number of forms/flows in use, number of submissions per day, etc..).

You will know when you need to increase allocated memory when you see two common errors appear in the Tomcat logfiles <frevvo-home>//tomcat/logs. You can tune the frevvo/tomcat installation by editing <frevvo-home>/tomcat/bin/setenv.bat on Windows and setenv.sh on Unix.

...

"%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-XX:+UseConcMarkSweepGC;-XX:+CMSClassUnloadingEnabled;-Djava.io.tmpdir=%CATALINA_BASE%\temp;-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager;-

Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties;-Dfile.encoding=UTF-8;-Djava.awt.headless=true;-Dspring.config.location=file:///%CATALINA_BASE%/conf/,file:///%CATALINA_BASE%/conf/frevvo-config.properties;-

Dderby.stream.error.file=%CATALINA_BASE%/logs/derby.log" --JvmMs 256 --JvmMx 1024

See the Apache 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.

...

By default, the <frevvo-home>\solr-7x.5x.0x\bin\solr script,(replace "x.x.x" with the version number) 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-7x.5x.0x\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.

...

1. Increase memory allocations for the frevvo and Insight (Solr) servers. Please see the documentation below..
2. Schedule a weekly restart of your frevvo and Insight (solr) servers. It usually takes a couple minutes to do this and is very helpful to prevent issues, memory leaks and potential server sluggishness and locks.
3. If you are using a SQL Server database for , be sure to configure Snapshot Isolation for that database.
4. Add thread count properties to the <frevvo-home>/tomcat/conf/frevvo-config.properties. These properties improve performance if you are experiencing slowness when using forms by increasing the CPU resources available to running form rules.
   
   Follow these steps:
   1. Stop .
   2. Navigate to <frevvo-home>/tomcat/conf.
   3. Edit the frevvo-config.properties file

   4. Add the following properties to the file and save the changes.
      

      Code Block
      frevvo.threadpool.coresize=40 frevvo.threadpool.maxsize=400 org.quartz.threadPool.threadCount=1

       

   5. Restart .
      

Troubleshooting

Solutions for memory errors are discussed below.

...

The insight server has its own log file under <frevvo-home>solr-7x.5x.0x\server\logs. If you see an Out of Memory exception in this log, review Insight Server Memory Settings to change the Insight Server heap size.

...