000034630 - RSA Identity Governance and Lifecycle 7.0.1 P01 installation gets stuck at message of undeploying current ear and deploying new customized ear message

Document created by RSA Customer Support Employee on Jan 13, 2017Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000034630
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0.1
IssueWhile installing patch P01 in RSA Identity Governance and Lifdecycle 7.0.1 the message Deploying new customized ear displays.  The next step does not complete.  The patch installation logs found in /home/oracle/Aveksa_7.0.1_P01/logs will show the installation stuck at the step below:
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
CauseThis 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.  

ResolutionConfigure the system to meet the memory requirements as mentioned on page 15 of the RSA Identity Governance and Lifecycle 7.0.1 Installation Guide.