...
...
...
...
...
...
...
...
...
...
...
...
| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Memory Configuration
The Tomcat The frevvo 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 serverthe frevvo server.
The first important step is to ensure that is that frevvo is installed on a machine with sufficient cpu CPU and ram. "Sufficient" depends on your usage your frevvo usage (number of users, number of forms/flows in use, number of submissions per day, etc.)
| Tip |
|---|
After making memory configuration changes you must restart the serverfrevvo server. |
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.
...
frevvo as a Windows service
If you are running as running frevvo 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:
...
By default, the <frevvo-home>\solr\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 many submissions. It may cause "out of memory" exceptions in the <frevvo-home>solr\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.
...
- Stop the Insight Server.
- Uncomment the set SOLR_JAVA_MEM statement in the OS-specific solr.in.* file (cmd for Windows, sh for Linux).
- Change the values.
For example, to increase the max heap size to 1G use: -Xms512m –Xmx1g. For *nix OS, make sure SOLR_HEAP is commented out. - Restart the Insight Server.
...
- Increase memory allocations for the frevvo and Insight (Solr) servers. Please see the documentation below.
- 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 in preventing issues, memory leaks and potential server sluggishness and locks.
- If you are using a SQL Server database for for frevvo, be sure to configure Snapshot Isolation for that database.
- 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:- Stop frevvo.
- Navigate to <frevvo-home>/tomcat/conf.
- Edit the frevvo-config.properties file
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
- Restart frevvo.
Troubleshooting
Solutions for memory errors are discussed below.
...
For example: -Xms512m to -Xmx1g. Make sure also that the machine where is where frevvo is installed has enough memory. If you change -Xmx to 1g your machine will need more then than 1g ram.
| Info |
|---|
If you are running as running frevvo as a Windows service, refer to this documentation to increase the memory settings. |
...
The insight server has its own log file under <frevvo-home>solr\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.
This is independent of which of frevvo which has its own log and its own heap size.