question Re: java.lang.IllegalStateException: Duplicate key error in SCCM Service Graph Connector in CMDB forum

java.lang.IllegalStateException: Duplicate key error in SCCM Service Graph Connector

Suvetha S — Mon, 22 Apr 2024 13:06:29 GMT

Hi All,

We are facing the below Import errors in our CMDB Integration Dashboard from SCCM Service Graph connector . Any idea how can we resolve this?

java.lang.IllegalStateException: Duplicate key 9b24a80cc38471d0762caa577a0131d7 (attempted merging values com.snc.cmdb.identify_reconcile.RecordCommitterForCi@d26ad4 and com.snc.cmdb.identify_reconcile.RecordCommitterForCi@ba8117)
at java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:133)
at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180)
at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
at com.snc.cmdb.identify_reconcile.DataSourceLastUpdateHistory.batchUpdateDataSourceLastUpdateHistory(DataSourceLastUpdateHistory.java:40)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.process(IdentificationEngine.java:1000)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.execute(IdentificationEngine.java:691)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.executeAndGenerateOutput(IdentificationEngine.java:613)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.execute(IdentificationEngine.java:570)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.createOrUpdateCI(IdentificationEngine.java:416)
at com.snc.cmdb.identify_reconcile.PayloadMerger.execute(PayloadMerger.java:256)
at com.snc.cmdb.identify_reconcile.PayloadMerger.mergeAndExecute0(PayloadMerger.java:324)
at com.snc.cmdb.identify_reconcile.PayloadMerger.mergeAndExecute(PayloadMerger.java:66)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.createOrUpdateCI(IdentificationEngine.java:391)
at com.snc.cmdb.identify_reconcile.listener.IREMessageListener.invokeIre(IREMessageListener.java:281)
at com.snc.cmdb.identify_reconcile.listener.IREMessageListener.onMessages(IREMessageListener.java:150)
at com.glide.db.impex.transformer.service.RobustImportSetTransformerDAO$ThrottlingListener.onMessages(RobustImportSetTransformerDAO.java:156)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.processBatch(RobustImportSetProcessor.java:125)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.transform(RobustImportSetProcessor.java:83)
at com.glide.system_import_set.ImportSetTransformerImpl.doRobustImportSetTransform(ImportSetTransformerImpl.java:166)
at com.glide.system_import_set.ImportSetTransformerImpl.transformAllMaps(ImportSetTransformerImpl.java:114)
at com.glide.system_import_set.ImportSetTransformerWorker.startWork(ImportSetTransformerWorker.java:40)
at com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:126)
at com.glide.worker.ProgressWorker.startAndWait(ProgressWorker.java:52)
at com.glide.worker.BackgroundProgressJob.execute(BackgroundProgressJob.java:59)
at com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:140)
at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:143)
at com.glide.schedule.JobExecutor.execute(JobExecutor.java:127)
at com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:338)
at com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$0(SchedulerWorkerThread.java:225)
at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
at com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:225)
at com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:101)

Re: java.lang.IllegalStateException: Duplicate key error in SCCM Service Graph Connector

Sandeep90 — Mon, 22 Apr 2024 19:45:37 GMT

@Suvetha S There is a defect for this and support can provide you the workaround, this happens only on VP6 and UP10 and upgrading will fix it.

Re: java.lang.IllegalStateException: Duplicate key error in SCCM Service Graph Connector

Sue15 — Wed, 01 May 2024 16:00:33 GMT

We just received this same error with the "Service Graph Connector for Observability - Dynatrace" when executing one of our SGO-Dynatrace ETLs. Could this be related to the same defect you mentioned? Is there a KB article or some other documentation explaining the cause of the error?

Thanks,

Sue

Re: java.lang.IllegalStateException: Duplicate key error in SCCM Service Graph Connector

Sandro Mattei — Tue, 07 May 2024 09:11:35 GMT

Hi.

I have symilar issue, which Defect do you mean? could you share the number/url?

Re: java.lang.IllegalStateException: Duplicate key error in SCCM Service Graph Connector

Pranav Patil — Wed, 08 May 2024 17:56:52 GMT

@Sandeep90 What is VP6 and UP10 ? Do we need to raise HI ticket to get more information on this ?

Re: java.lang.IllegalStateException: Duplicate key error in SCCM Service Graph Connector

Sue15 — Wed, 15 May 2024 18:54:32 GMT

FYI - I opened a case with ServiceNow Support on our issue with getting this same error with "Service Graph Connector for Observability - Dynatrace" when executing our SGO-Dynatrace ETLs. According to them, this issue was seen in Vancouver Patch 6 and was fixed in Vancouver Patch 7. We've recently upgraded our instances from Vancouver Patch 6 to Vancouver Patch 8 Hotfix 3, and so far, we have not seen the error since the upgrade. (The most recent upgrade, in our production instance, was this past weekend.)

Re: java.lang.IllegalStateException: Duplicate key error in SCCM Service Graph Connector

Pranav Patil — Wed, 05 Jun 2024 17:57:35 GMT

Hi @Sue15

Did this upgrade also helped with proper data population of Server data , I have observed one issue where the name of the server is getting changed to unexpected name and creating duplicates

After Patch upgrade did this help to maintain the data quality ?