on Jan 5, 2017Article Content
| Article Number | 000033770 |
| Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: 7.x |
| Issue | When starting AFX, some connectors fail to go into a Running state. This is most often seen after an RSA Identity Governance & Lifecycle upgrade or after adding many new connectors to the existing configuration. The AFX log files located in $AFX_HOME/esb/logs, $AFX_HOME/mmc-console/logs, and $AFX_HOME/activemq/data show OutOfMemoryError errors. For example, 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) |
| Cause | The ulimits in /etc/security/limits.conf are not configured appropriately causing AFX to run out of memory. |
| Resolution | Please refer to RSA Knowledge Base Article 000038069 -- What are the recommended ulimit settings in /etc/security/limits.conf for use with RSA Identity Governance & Lifecycle for instructions on setting ulimits to the appropriate values for use with RSA Identity Governance & Lifecycle and AFX. |