Multi-app Entitlement Data Collector (MAEDC) fails with DuplicateNameException in RSA Identity Governance & Lifecycle
Originally Published: 2019-05-13
Article Number
Applies To
RSA Version/Condition: 7.0.2
Issue
03/25/2018 03:10:51.084 ERROR (Exec Task Consumer#0) [com.aveksa.server.xfw.TaskExecutor] Failed method=Execute ExecutionTask[TaskID=1111111 RunID=60000 Source=1251 Type=DataPreProcessing Status=InProgress]
com.aveksa.server.xfw.ExecutionException: com.aveksa.server.collector.DataProcessorException: com.aveksa.server.core.DuplicateNameException: Name of Child Collector-9999-ChildMultiApp
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeFullTask(DataPreProcessingExecutor.java:147)
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeTask(DataPreProcessingExecutor.java:64)
at com.aveksa.server.xfw.TaskExecutor.execute(TaskExecutor.java:99)
at com.aveksa.server.xfw.ExecutionTaskQueue$Worker.run(ExecutionTaskQueue.java:116)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.aveksa.server.collector.DataProcessorException: com.aveksa.server.core.DuplicateNameException: Name of Child Collector-9999-ChildMultiApp
at com.aveksa.server.xfw.DefaultEntitlementDataPreProcessingFilter.updateMAEDCProcessData(DefaultEntitlementDataPreProcessingFilter.java:419)
at com.aveksa.server.xfw.DefaultEntitlementDataPreProcessingFilter.process(DefaultEntitlementDataPreProcessingFilter.java:259)
at com.aveksa.server.xfw.DefaultEntitlementDataPreProcessingFilter.process(DefaultEntitlementDataPreProcessingFilter.java:179)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:85)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:64)
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeFullTask(DataPreProcessingExecutor.java:136)
... 4 more
Caused by: com.aveksa.server.core.DuplicateNameException: Name of Child Collector-9999-ChildMultiApp
at com.aveksa.server.core.Application.createEntitlementDataCollector(Application.java:2866)
at com.aveksa.server.core.Application.createChildMultiAppEDC(Application.java:2959)
at com.aveksa.server.xfw.DefaultEntitlementDataPreProcessingFilter.updateMAEDCProcessData(DefaultEntitlementDataPreProcessingFilter.java:393)
... 9 more
com.aveksa.server.xfw.ExecutionException: com.aveksa.server.collector.DataProcessorException: com.aveksa.server.core.DuplicateNameException: Name of Child Collector-9999-ChildMultiApp
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeFullTask(DataPreProcessingExecutor.java:147)
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeTask(DataPreProcessingExecutor.java:64)
at com.aveksa.server.xfw.TaskExecutor.execute(TaskExecutor.java:99)
at com.aveksa.server.xfw.ExecutionTaskQueue$Worker.run(ExecutionTaskQueue.java:116)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.aveksa.server.collector.DataProcessorException: com.aveksa.server.core.DuplicateNameException: Name of Child Collector-9999-ChildMultiApp
at com.aveksa.server.xfw.DefaultEntitlementDataPreProcessingFilter.updateMAEDCProcessData(DefaultEntitlementDataPreProcessingFilter.java:419)
at com.aveksa.server.xfw.DefaultEntitlementDataPreProcessingFilter.process(DefaultEntitlementDataPreProcessingFilter.java:259)
at com.aveksa.server.xfw.DefaultEntitlementDataPreProcessingFilter.process(DefaultEntitlementDataPreProcessingFilter.java:179)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:85)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:64)
at com.aveksa.server.xfw.DataPreProcessingExecutor.executeFullTask(DataPreProcessingExecutor.java:136)
... 4 more
Caused by: com.aveksa.server.core.DuplicateNameException: Name of Child Collector-9999-ChildMultiApp
at com.aveksa.server.core.Application.createEntitlementDataCollector(Application.java:2866)
at com.aveksa.server.core.Application.createChildMultiAppEDC(Application.java:2959)
at com.aveksa.server.xfw.DefaultEntitlementDataPreProcessingFilter.updateMAEDCProcessData(DefaultEntitlementDataPreProcessingFilter.java:393)
... 9 more
Cause
The processing phase of a collection is where collected data from the end point that has been successfully collected into flat files on the RSA Identity Governance & Lifecycle server, is being pulled into the database. A failure at this phase of a collection indicates a problem within the database. In this case, there is a duplicate name failure on the Child Multi-app Collector called Name of Child Collector-9999-ChildMultiApp.
The link between the Application and the Child Multi-app collector is not being recognized, so it is trying to create a new Child collector with the same name. The creation of the Child Multi-app collector fails because the name is already in use.
The root cause as to why the link between the Application and the ChildMultiApp is not recognized is not known at this time.
Resolution
Related Articles
How a Multi-App Entitlement Collector (MAEDC) resolves entitlement relationships with accounts and groups collected by a M… Number of Views How to configure a JSON response in AFX connector capabilities to parse single or multi-valued responses in RSA Identity G… Number of Views Troubleshooting Wildfly clustering Multi-cast connectivity for RSA Via Lifecycle and Governance Number of Views 'Multi App Collector : 'Admin' privilege does not allow editing of the collector definition as expected in RSA Identity Go… Number of Views How (and why) do I enable Authentication Manager Prime multi-tenant mode? Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?
