Here are the recommended hardware and memory requirements for your in-house Live Forms server.
The minimum recommended hardware configuration for your Live Forms server is:
- 2 gigahertz (GHz) 32-bit (x86) or 64-bit (x64) processor
- 4 gigabyte (GB) of system memory
- 100 GB hard drive
However you must size your hardware platform to your specific form usage characteristics. As the number of concurrent users and forms increases so must the system memory. For a medium use production server consider increasing the JVM RAM allocation to 6 or 8 gigabytes. Refer to the memory configuration topic below.
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 frevvo server.
The first important step is to ensure that frevvo is installed on a machine with sufficient cpu and ram. "Sufficient" depends on your frevvo usage (number of users, number of forms in use, number of submissions per day, etc..).
After making memory configuration changes you must restart the frevvo 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.
You'll see something like this in setenv.[bat,sh]:
OutOfMemoryError: Java heap space
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.OutOfMemoryError: Java heap space
To solve this edit setenv.[bat,sh] to increase the minimum and maximum heap size via the parameters: -Xmx and -Xms.
For example: -Xmx512m to -Xmx1g. Make sure also that the machine where frevvo is installed has enough memory installed. If you change -Xmx to 1g your machine will need more then 1g ram.
OutOfMemoryError: PermGen space
MemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
Java has a fixed space allocated for classes and other statics that is usually enough in normal cases, but could be quickly filled up if there is on the fly code generation or significant business logic in your forms.
To solve this edit setenv.[bat,sh] increase the maximum perm size via the paramenter: -XX:MaxPermSize
For example: -XX:MaxPermSize=128M