AEM custom indexes show /dummy path after SIM deployment due to malformed diff.json
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article explains why custom indexes in Adobe Experience Manager may display a /dummy path after deployment with Smart Index Management (SIM), and provides steps to resolve the issue caused by a malformed diff.json file.
Description description
Environment
- Adobe Experience Manager (AEM), all versions
Symptoms
- After deploying custom indexes using the Smart Index Management (SIM) tool, all fully custom indexes display /dummy as their path.
- The indexes are effectively retired or disabled.
- The following error appears in logs, but is not the root cause:
This DocumentNodeStore is disposed- The issue is not reproducible after correcting the configuration.
Cause
A malformed diff.json file (such as a missing closing brace) causes SIM to treat all affected custom indexes as removed. With dummy-removal mode enabled, this results in new Lucene index versions with includedPaths=“/dummy” and queryPaths=“/dummy”, effectively disabling those indexes.
Resolution resolution
Follow the steps below to resolve the issue:
- Review the diff.json file used for SIM deployment.
- Open the diff.json file and check for syntax errors, especially missing or misplaced closing braces (
}). Correct the JSON structure. - Ensure that each custom index definition is properly closed and that top-level indexes are not inadvertently nested within others.
- For example, the closing brace for an index rule should appear before the next top-level index definition.
- Redeploy the corrected diff.json file using SIM.
- After redeployment, verify that custom indexes now show the intended paths and not /dummy.
recommendation-more-help
experience-cloud-kcs-help-kbarticles