000030763 - How to reduce the opportunity of JBoss Heap Dump / out of memory occurrences with Identity Management and Governence

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

Article Content

Article Number000030763
Applies ToRSA Product Set: Identity Management and Governance
Platform: JBoss
 
IssueWith Identity Management and Governance v6.0.x through and including v6.9.x running with a JBoss Application server a Heap Dump / out of memory condition may occur more frequently as a result of an incorrectly defined JBoss configuration.
ResolutionModify the following file located on the Identity Management and Governance linux server as the linux user named 'oracle'
/home/oracle/jboss-4.2.2.GA/server/default/deploy/ejb3-interceptors-aop.xml
Modify this section:
From:
<domain name="Stateless Bean">
...
  <annotation expr="!class(@org.jboss.annotation.ejb.PoolClass)">
     @org.jboss.annotation.ejb.PoolClass (value=org.jboss.ejb3.ThreadlocalPool.class, maxSize=30, timeout=10000)
  </annotation>
</domain>
To:
<domain name="Stateless Bean">
...
  <annotation expr="!class(@org.jboss.annotation.ejb.PoolClass)">
     @org.jboss.annotation.ejb.PoolClass (value=org.jboss.ejb3.StrictMaxPool.class, maxSize=30, timeout=10000)
  </annotation>
</domain>
 
 
Note there are several references to org.jboss.ejb3.ThreadlocalPool.class in the file, only changes to the “Stateless Bean” section is required.  
After the change is made Identity Management and Governance needs to be restarted for this to take effect.   This can be accomplished by running 
acm stop
acm start

Further the above change will automatically to be applied/implemented commencing with 6.9.1 P04 and engineering ticket ACM-53163
 

Attachments

    Outcomes