Here are the recommended hardware and memory requirements for your in-house server.
...
Code Block | ||
---|---|---|
| ||
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:
Code Block | ||
---|---|---|
| ||
"%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-XX:MaxPermSize=156m;-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" --JvmMs 256 --JvmMx 1024 |
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.
Follow these steps:
- 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.
Code Block |
---|
#REM Increase Java Min/Max Heap as needed to support your indexing / query needs #SOLR_HEAP="512m" # Expert: If you want finer control over memory options, specify them directly # Comment out SOLR_HEAP if you are using this though, that takes precedence set SOLR_JAVA_MEM="-Xms512m -Xmx1g"Xmx512m |
Troubleshooting
Solutions for memory errors are discussed below.
...
For example: -Xms512m to -Xmx1g. Make sure also that the machine where is installed has enough memory installed. If you change -Xmx to 1g your machine will need more then 1g ram.
...
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
Out of Memory Errors in the Insight Server log:
...
This is independent of which has its own log and its own heap size.
set
CATALINA_OPTS=%CATALINA_OPTS% -Xms256m -Xmx1024m