After starting AFX, some AFX Connectors fail to go to a Running state due to Out of Memory errors in RSA Identity Governance & Lifecycle
Originally Published: 2016-08-12
Article Number
Applies To
RSA Version/Condition: 7.x
Issue
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)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ 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
Resolution
Related Articles
Configure Cisco IOS for password integration to go into enable (admin) mode. - RSA Authentication Manager 115Number of Views Fulfillment Workflow gets canceled and change request goes to rejected state in RSA Governance & Lifecycle 14Number of Views After starting AFX, some AFX Connectors failed to be deployed successfully due to Out of Memory errors in RSA Governance &… 62Number of Views How to disable SecurID Tokens before they go into Next Token Mode 149Number of Views Error when going into the Event Viewer 23Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?