AFX connectors in "Not Deployed" state in RSA Governance & Lifecycle
Last Modified: 2024-01-16
Article Number
Applies To
- RSA Governance & Lifecycle 8.0.0
- Remote AFX installations only
Issue
The AFX server shows all connectors in "Not Deployed" state.
The esb.AFX-MAIN.log shows an error "Cannot run program "jar". INFO level log message.
INFO 2023-10-16 09:26:04,183 [[MuleRuntime].abcd.6291: [10-AFX-MAIN].PRIMARY_REQUEST.BLOCKING @4c2a6cc9] [processor: PRIMARY_REQUEST/processors/6/route/2/processors/4; event: 03914640-6c06-11ee-b8e1-1234a7fdf3c9] ConnectorDeploymentManagerImpl: Jar command execution is failed in /home/afx/AFX/esb/binary-repo/0/AFX-CONN-AD-CONNECTOR-archetype java.io.IOException: Cannot run program "jar": error=2, No such file or directory
Cause
Resolution
Related Articles
Decision node in RSA Identity Governance & Lifecycle ignores "Contains at least one violation" Number of Views AFX is unresponsive and one or more AFX Connectors are in a Not Deployed state in RSA Identity Governance & Lifecycle Number of Views No enum constant com.aveksa.server.report.Report.SaveAsType.XLS reported in RSA Identity Governance & Lifecycle Number of Views RSA Identity Governance and Lifecycle - Microsoft Exchange Application Guide Number of Views AFX Connectors remain in a Deployed state and ActiveMQ is not running in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
Don't see what you're looking for?
