000033770 - When starting RSA Via Lifecycle and Governance 7.0 Access Fulfillment Express (AFX) services, some of the connectors are failing due to Out of Memory errors

Document created by RSA Customer Support Employee on Jan 5, 2017Last modified by RSA Customer Support Employee on Apr 26, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033770
Applies ToRSA Product Set: RSA Via Lifecycle and Governance
RSA Product/Service Type: Access Fulfillment Express (AFX)
RSA Version/Condition: 7.0
Platform: Linux
O/S Version: Red Hat Enterprise Linux 6.x
IssueWhen upgrading from RSA Via Lifecycle and Governance from any version to any version, if the customer faced some issues with the AFX services and shows Out of Memory errors in the ESB, MMC and ActiveMQ logs found in $AFX_HOME/esb/logs, $AFX_HOME/mmc-console/logs, and $AFX_HOME/activemq/data respectively.
 
INFO  2016-07-12 14:33:35,764 [WrapperListener_start_runner] org.mule.module.launcher.log4j.ArtifactAwareRepositorySelector: Found logging config for application 'AFX-SETTINGS-OpenLDAP' 
at 'file:/aveksa_afx_tst/AFX/mule/apps/AFX-SETTINGS-OpenLDAP/classes/log4j.xml'
ERROR 2016-07-12 14:33:36,463 [WrapperListener_start_runner] org.mule.module.launcher.DefaultArchiveDeployer:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Failed to deploy artifact 'AFX-SETTINGS-OpenLDAP', see   +
+ below                                                    +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
org.mule.module.launcher.DeploymentStartException: OutOfMemoryError: unable to create new native thread
        at org.mule.module.launcher.application.DefaultMuleApplication.start(DefaultMuleApplication.java:155)
        at org.mule.module.launcher.artifact.ArtifactWrapper$4.execute(ArtifactWrapper.java:98)
        at org.mule.module.launcher.artifact.ArtifactWrapper.executeWithinArtifactClassLoader(ArtifactWrapper.java:129)
        at org.mule.module.launcher.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:108)
ResolutionChanging the limits is the right solution.
Our current general guidance for the limits is as follows:  From ACM-45939 (Problematic LDAP MAEDC Collector has poor performance and occasional failure with ORA-04030 out of process memory error), these are recommended to be at least the following:
  • Open file descriptors nofile - soft at least 1024, hard at least 65536
  • Number of processes available to a single user nproc - soft at least 2047, hard at least 16384
  • Size of the stack segment of the process stack - soft at least 10240 KB, hard at least 10240 KB and at most 32768 KB
To check resource limits, log in as an installation owner (oracle) and run these commands:
  1. Check the soft and hard limits for the file descriptor setting. Ensure that the result is in the recommended range; for example:
$ ulimit -Sn
1024
$ ulimit -Hn
65536

  1. Check the soft and hard limits for the number of processes available to a user. Ensure that the result is in the recommended range; for example:
$ ulimit -Su
2047
$ ulimit -Hu
16384

  1. Check the limits for the stack setting. Ensure that the result is in the recommended range; for example:
$ ulimit -Ss
10240
$ ulimit -Hs
32768

You can check the update the resource limits in the /etc/security/limits.conf configuration file for the installation. However, note that the configuration file is distribution specific. Contact system administrator for distribution specific configuration file information.
As an example, below are entries in /etc/security/limits.conf that set the above values for the 'oracle' user:
oracle soft nofile 1024
oracle hard nofile 65536
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft stack 10240
oracle hard stack 32768

Attachments

    Outcomes