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
RFE in SilverCat (Configuration Manager) to Remove Dashes from Concatenated Attributes in RSA Web Threat Detection 16Number of Views What are the basic requirements for RSA Web Threat Detection to capture our website's traffic? 18Number of Views Artifacts to gather in RSA Identity Governance & Lifecycle 3.99KNumber of Views Collector or AFX Connector or JSP or Collector or Connector TEST fails with "PKIX path building failed" in RSA Governance … 492Number of Views How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle 1.67KNumber of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?