AFX Connector fails with java.lang.NoClassDefFoundError in RSA Governance & Lifecycle
Last Modified: 2026-10-02
Article Number
Applies To
- RSA Governance & Lifecycle 8.0
Issue
An attempt to fulfill-request/test-connector-capability of a connector may fail with the following error, observed on the UI and logged in the corresponding connector log file <AFX_HOME>/esb/logs/esb.AFX-CONN-<connector-name>.log:
Cause: java.lang.NoClassDefFoundError - <path-to-a-class>
The class path shown in the above error depends on the connector type and the capability being tested. For example, the following class paths have been reported:
- LDAP Connector
java.lang.NoClassDefFoundError - com/aveksa/LdapVerb'.
- RESTful Web Service connector:
java.lang.NoClassDefFoundError - com/jayway/jsonpath/internal/path/ArrayIndexOperation
java.lang.NoClassDefFoundError - com/jayway/jsonpath/Predicate
- Google Apps connector:
java.lang.NoClassDefFoundError - com/google/api/client/repackaged/com/google/common/base/Splitter
Cause
Resolution
This is a known issue related to the AFX Server component's class loader. While several scenarios have been addressed in various patches up to and including RSA Governance & Lifecycle 8.0 P08, intermittent
java.lang.NoClassDefFoundError exceptions may still occur on later patches.Ensure that your RSA Governance & Lifecycle 8.0 deployment is upgraded to the latest available patch level to prevent encountering previously resolved class-loader issues.
If the class-loader issue persists despite being on the latest patch level:
- If the impact is high and the provisioning service must be restored immediately, apply the workaround. Note that this limits our ability to identify the root cause.
- If impact is low, please open an RSA Support Case and share the following diagnostic artifacts prior to applying the workaround so we can analyze the issue for a permanent resolution.
- Log Artifact zip - generated from Admin > Diagnostics > Log Artifact
- AFX/Connector Log Files - Compressed copy of the $AFX_HOME/esb/logs directory
- Connector Export - Export of the affected connector
Workaround
Related Articles
AFX Connectors remain in a Deployed state and Port 8585 already in use error in RSA Identity Governance & Lifecycle Number of Views How to make the Oracle INITCAP function work to format raw data collected from a csv file during Identity Data Collection … Number of Views RSA Governance & Lifecycle Microsoft Exchange Connector Application Guide Number of Views RSA Identity Governance and Lifecycle - Microsoft Exchange Application Guide Number of Views RFE in SilverCat (Configuration Manager) to Remove Dashes from Concatenated Attributes in RSA Web Threat Detection Number of Views
Don't see what you're looking for?
