AEM Eventing - DUMMY Change Type - Traversal Log | Community
Skip to main content
NageshRaja
NageshRaja
Level 5
January 22, 2025
Solved

AEM Eventing - DUMMY Change Type - Traversal Log

  • January 22, 2025
  • 3 replies
  • 856 views

Hi All,

 

We are seeing in our environments

 

22.01.2025 08:00:11.490 [cm-p10000-e100000-aem-author-bc5d5000d-bhfqz] *WARN* [sling-oak-observation-5] com.adobe.aem.sites.eventing.impl.producer.PageProducerStrategy Invalid change type detected: DUMMY

22.01.2025 08:00:11.518 [cm-p10000-e100000-aem-author-bc5d5000d-bhfqz] *WARN* [sling-oak-observation-5] org.apache.jackrabbit.oak.query.QueryImpl Traversal query (query without index): SELECT * FROM [cq:Page] AS page INNER JOIN [cq:PageContent] AS pageContent ON ISCHILDNODE(pageContent, page) WHERE page.[jcr:path] LIKE '/content/brandX/sitemap_en.xml' AND (ISDESCENDANTNODE(page ,'/content') OR ISDESCENDANTNODE(page ,'/etc') OR ISDESCENDANTNODE(page ,'/conf')); called by com.adobe.aem.sites.eventing.impl.repository.PersistenceQueryManagerImpl.lambda$getPageDetails$3; consider creating an index

 

We tried to create a lucene index based on the above query but that also has not worked.

The query is not triggered by our custom code.

 

Checking the logs we can see the PageProducerStrategy detected a DUMMY change type which is invalid.
Not sure what exactly is causing this DUMMY event triggering but what is the best way to fix this?

 

BR,

Nagesh

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by NageshRaja

Adobe support provided the below reply for this -
The traversal was from product code that happened via a commit from our internal engineering.
That query is unintended bug and our sites team removed the query entirely from the code-base.

Fix for this will be available in the upcoming latest version of AEM.
Whenever sites-eventing-0.0.66 is added to quickstart.

This should get fixed in the release before March 20th.

3 replies

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
January 22, 2025

Fix the "DUMMY" change type: Check if any custom code or workflows are causing the invalid "DUMMY" event. It could be something in your setup that’s triggering this. Try to figure out where this event is coming from by looking through your event listeners or logs. Review any custom event listeners or workflows in your environment. It could be useful to search the codebase for instances where events are being fired with a "DUMMY" change type. You may need to debug these areas to understand why it’s happening.

Resolve the query indexing issue: Make sure the Lucene index is set up correctly for the nodes and properties being queried, like cq:Page and cq:PageContent.Use the Oak Index Manager in AEM to review and set up an index if necessary.

Improve performance: Make sure that the queries are well-optimized with proper indexing to prevent performance issues.

SELECT * FROM [cq:Page] AS page INNER JOIN [cq:PageContent] AS pageContent ON ISCHILDNODE(pageContent, page) WHERE page.[jcr:path] LIKE '/content/brandX/sitemap_en.xml' AND (ISDESCENDANTNODE(page ,'/content') OR ISDESCENDANTNODE(page ,'/etc') OR ISDESCENDANTNODE(page ,'/conf'));

The query is being executed without an index, which can negatively impact performance. Double-check the Lucene index configuration. Ensure it’s targeting the correct nodes (cq:Page, cq:PageContent, etc.) and properties (like jcr:path). Consider creating a custom index if the existing index isn't sufficient. This can be done through the Oak Index Manager in AEM to optimize performance for this query. Even though the query isn't triggered by custom code, it may still be part of AEM's internal eventing or content management mechanisms.

    NageshRaja
    NageshRajaAuthor
    Level 5
    January 30, 2025

    Nope there's nothing in the custom application code that'd trigger DUMMY event type.

    The problem is sitemap.xml is a nt:file while the query is looking for cq:Page node which doesn't exist.

    So even with the correct index for nt:file the query triggered itself is incorrect.

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    March 5, 2025

    @nageshraja Did you find the suggestion helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

    Kautuk Sahni
    NageshRaja
    NageshRajaAuthorAccepted solution
    Level 5
    March 11, 2025

    Adobe support provided the below reply for this -
    The traversal was from product code that happened via a commit from our internal engineering.
    That query is unintended bug and our sites team removed the query entirely from the code-base.

    Fix for this will be available in the upcoming latest version of AEM.
    Whenever sites-    eventing-0.0.66 is added to quickstart.

    This should get fixed in the release before March 20th.

      Terms & ConditionsAccessibility statement

      Loading footer...