...

By default, the <frevvo-home>\solr-67.65.20\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-67.65.20\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.

...