RSA Identity Governance and Lifecycle 7.0.1 P01 installation gets stuck at message of undeploying current ear and deploying new customized ear message
Originally Published: 2017-01-04
Article Number
Applies To
RSA Version/Condition: 7.0.1
Issue
Creating aveksa.ear file for deployment [zip] Building zip: /tmp/customizeACM/aveksa.war [zip] Building zip: /tmp/customizeACM/aveksa.ear [copy] Copying 1 file to /home/oracle/archive Undeploying current ear... Deploying new customized ear... this may take a while...The server.log found in /home/oracle/wildfly-8.2.0.Final/standalone/log has the following java.lang.OutOfMemoryError: PermGen error:
2016-12-02 18:23:52,752 WARN [org.jboss.modules] (Thread-346) Failed to define class com.thoughtworks.xstream.converters.extended.ThrowableConverter
in Module "deployment.aveksa.ear:main" from Service Module Loader: java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_79]
at java.lang.ClassLoader.defineClass(ClassLoader.java:800) [rt.jar:1.7.0_79]
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.3.Final]
The message below can be seen when starting the RSA Identity Governance and Lifecycle application:The server's installed RAM seems to be below the minimum requirement
for RSA Identity Governance and Lifecycle, and AFX is installed on this system,
which can potentially cause memory unavailable messages.
Hardcoding Wildfly to use -Xmx1024m -XX:MaxPermSize=256M heap settings
for RSA Identity Governance and Lifecycle, and AFX is installed on this system,
which can potentially cause memory unavailable messages.
Hardcoding Wildfly to use -Xmx1024m -XX:MaxPermSize=256M heap settings
Cause
This issue occurs because there is not enough free JVM memory. This occurs when the system does not meet the minimum RAM requirements as specified in the RSA Identity Governance and Lifecycle 7.0.1 Installation Guide.
The problem is the setting of MaxPermSize=256M needs to be set to MaxPermSize=512M, as noted on page 57 of the Installation Guide. This setting is configured in the /etc/init.d/aveksa_server script based on the physical RAM of the machine.
Resolution
Related Articles
Generate a Report of the Current Configuration Settings Number of Views After importing a database from another system, the workflow monitoring tab shows both the current node name and the origi… Number of Views Error "Unable to retrieve current platform specification" when upgrading RSA Authentication Manager 8.x Number of Views Escalation Workflow "Reviewer Reassign" transferring review items to new reviewers only and the current reviewers are remo… Number of Views RSA Announces Updated Capabilities for Unstructured Data Collection for Data Access Governance DAG Module and End of Prima… Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA-2026-07: RSA Identity Router Security Update for Third-Party Component Vulnerabilities Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?
