When extending the Root General Template for Databases, all Database Connectors using that root template stop working in RSA Governance & Lifecycle
Originally Published: 2025-01-06
Article Number
Applies To
RSA Product Set: RSA Governance & Lifecycle
RSA Version/Condition: 8.0 GA- 8.0 P04
Issue
Upon extending the Generic Database templates with new jar files, not a single connector using the root database template will deploy. In the esb.AFX-MAIN.log:
INFO 2024-10-28 03:09:31,884 [[MuleRuntime].uber.3316: [10-AFX-MAIN].PRIMARY_REQUEST.BLOCKING @503e66f9] [processor: PRIMARY_REQUEST/processors/5/route/2/processors/4; event: 897c94c0-94fb-11ef-8f1d-005056012b47] MavenHelper: Executing maven command : mvn package -o, Inside generateConnectorApplicationJar()
INFO 2024-10-28 03:09:44,638 [[MuleRuntime].uber.3316: [10-AFX-MAIN].PRIMARY_REQUEST.BLOCKING @503e66f9] [processor: PRIMARY_REQUEST/processors/5/route/2/processors/4; event: 897c94c0-94fb-11ef-8f1d-005056012b47] MavenHelper: Maven execution result inside generateConnectorApplicationJar() method [Status code = 1 ], Maven result
[INFO] Scanning for projects...
[INFO]
[INFO] ------------< com.aveksa:AFX-CONN-Menna-Postgres-Connector >------------
[INFO] Building AFX-CONN-Menna-Postgres-Connector 1.0.0
[INFO] from pom.xml
[INFO] --------------------------[ mule-application ]--------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.320 s
[INFO] Finished at: 2024-10-28T03:09:44-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project AFX-CONN-Menna-Postgres-Connector: Could not resolve dependencies for project com.aveksa:AFX-CONN-Menna-Postgres-Connector:mule-application:1.0.0: Failed to collect dependencies at com.aveksa:AFX_GenericDB_teiid-10.3.5-jdbc:jar:1.0.0: Failed to read artifact descriptor for com.aveksa:AFX_GenericDB_teiid-10.3.5-jdbc:jar:1.0.0: The following artifacts could not be resolved: org.teiid:teiid-parent:pom:10.3.5 (absent): Cannot access anypoint-exchange-v2 (https://maven.anypoint.mulesoft.com/api/v2/maven) in offline mode and the artifact org.teiid:teiid-parent:pom:10.3.5 has not been downloaded from it before. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
INFO 2024-10-28 03:09:44,638 [[MuleRuntime].uber.3316: [10-AFX-MAIN].PRIMARY_REQUEST.BLOCKING @503e66f9] [processor: PRIMARY_REQUEST/processors/5/route/2/processors/4; event: 897c94c0-94fb-11ef-8f1d-005056012b47] MavenHelper: Copying Connector Jar From /home/oracle/AFX/esb/appStaging/AFX-CONN-Menna-Postgres-Connector/target/AFX-CONN-Menna-Postgres-Connector-1.0.0-mule-application.jar to /home/oracle/AFX/esb/apps/AFX-CONN-Menna-Postgres-Connector.jar
ERROR 2024-10-28 03:09:44,638 [[MuleRuntime].uber.3316: [10-AFX-MAIN].PRIMARY_REQUEST.BLOCKING @503e66f9] [processor: PRIMARY_REQUEST/processors/5/route/2/processors/4; event: 897c94c0-94fb-11ef-8f1d-005056012b47] MavenHelper: Error While deploying connector into esb/apps folder
java.io.FileNotFoundException: /home/oracle/AFX/esb/appStaging/AFX-CONN-Menna-Postgres-Connector/target/AFX-CONN-Menna-Postgres-Connector-1.0.0-mule-application.jar (No such file or directory)
at java.io.FileInputStream.open0(Native Method) ~[?:1.8.0_422]
at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:1.8.0_422]
at java.io.FileInputStream.<init>(FileInputStream.java:138) ~[?:1.8.0_422]
at com.aveksa.common.utils.FileUtils.copy(FileUtils.java:104) ~[common-1.0.0.jar:?]
at com.aveksa.afx.server.component.helper.MavenHelper.deployConnectorJar(MavenHelper.java:394) ~[afx-server-1.0.0.jar:?]
at com.aveksa.afx.server.manager.deployment.ConnectorDeploymentManagerImpl.generateConnectorApplication(ConnectorDeploymentManagerImpl.java:315) ~[afx-server-1.0.0.jar:?]
at com.aveksa.afx.server.manager.deployment.ConnectorDeploymentManagerImpl.generateConnectorApplication(ConnectorDeploymentManagerImpl.java:50) ~[afx-server-1.0.0.jar:?]
at com.aveksa.afx.server.manager.deployment.BaseDeploymentManager.deploy(BaseDeploymentManager.java:209) ~[afx-server-1.0.0.jar:?]Cause
The custom jar for the connector was placed in the M2 repository with an embedded POM instead of the AFX POM, which caused it to attempt installing the dependency jars. Changes have been made for both connector deployment and Test Connector Settings to add the custom jar with the AFX pom
Resolution
This issue is resolved in the following RSA Governance & Lifecycle patches:
- RSA Identity Governance & Lifecycle 8.0 P06 and later versions/ patches
Related Articles
Windows collection has stopped working but did work in the past. 140Number of Views WTD WebPost Notification Stop Working 2Number of Views CrowdStrike Falcon Next-Gen SIEM – RSA Ready Implementation Guide 14Number of Views ADFS stopped working after TLS 1.2 cloud enforcement in SecurId Access 232Number of Views CrowdStrike Falcon Next-Gen SIEM - Authentication Manager - RSA Ready Implementation Guide 6Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA-2026-07: RSA Identity Router Security Update for Third-Party Component Vulnerabilities Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?