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
Indirect Relationship Processing fails with ORA-30926 and 'ORA-06512: at "AVUSER.CE_USERS" ' errors after Migration to 7.0… 922Number of Views Emails from workflow approval/fulfillment nodes are not generated and sent due to error "Illegal hex characters in escape … 83Number of Views Generate a Report of the Current Configuration Settings 29Number of Views 8.5P4 linux webtier shows online-reinstall required 345Number of Views Error "Request Entity Too Large" when upgrading RSA Authentication Manager from versions (8.2 SP1 up to 8.4 P13) to 8.5 360Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Enable SSH from a console connection if the Operations Console is not available for RSA Authentication Manager 8.x Download RSA SecurID Access Cloud Administration audit logs using Cloud Administration REST API CLU RSA Authentication Manager Patch Updates
Don't see what you're looking for?