RSA Version/Condition: 7.0.2
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
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.
Related Articles
How a Multi-App Entitlement Collector (MAEDC) resolves entitlement relationships with accounts and groups collected by a M… 158Number of Views Troubleshooting Wildfly clustering Multi-cast connectivity for RSA Via Lifecycle and Governance 195Number of Views Multi-App Collector Circuit Breaker trips incorrectly in SecurID Governance & Lifecycle 218Number of Views 'Multi App Collector : 'Admin' privilege does not allow editing of the collector definition as expected in RSA Identity Go… 25Number of Views RSA Governance & Lifecycle Recipes: Weekly Trending Multi Series Chart - Joiners & Leavers 15Number of Views