Memory errors relating Java Virtual Machine (JVM) Space, Swap Space or PermSize in JBOSS for EngageOne Server Administration
Issue
EngageOne® Admin deployed with JBOSS giving errors about memory related issues for JVM in relation to swap size and perm size when performing specific functions.
Cause
The settings for the swap space and max perm size are not set high enough for the operation.
Default settings can be found in <JBoss_install_path>\bin\run.bat:
rem JVM memory allocation pool parameters. Modify as appropriate.
set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx256m -XX:MaxPermSize=256m
Default settings can be found in <JBoss_install_path>\bin\run.bat:
rem JVM memory allocation pool parameters. Modify as appropriate.
set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx256m -XX:MaxPermSize=256m
Resolution
UPDATED: June 25, 2018Edit the default settings in run.bat to a high enough level to allow the attempted operation (may required several attempts to get the value correct):
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx256m -XX:MaxPermSize=256m
Initially, suggestion is to double these values and try the operation again, and continue doubling until operation completes.
It will be necessary to restart JBoss after each change.
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx256m -XX:MaxPermSize=256m
Initially, suggestion is to double these values and try the operation again, and continue doubling until operation completes.
It will be necessary to restart JBoss after each change.
