While using ACS Audit log search getting java.lang.UnsupportedOperationException: The query read or traversed more than 300000 ... processing was stopped. | Community
Skip to main content
Umesh_Thakur
Community Advisor
Umesh_ThakurCommunity Advisor
Community Advisor
October 1, 2020
Solved

While using ACS Audit log search getting java.lang.UnsupportedOperationException: The query read or traversed more than 300000 ... processing was stopped.

  • October 1, 2020
  • 1 reply
  • 1116 views

Dear Members,

I am using audit log search in on of my environment but due to "

java.lang.UnsupportedOperationException: The query read or traversed more than 300000 nodes. To avoid affecting other tasks, processing was stopped.

" it is not working even with the path where, there in no activation or any kind of modification has had happened.

To Resolve the issue I have purged the page audit log several time with the Minimum age at 1 and I also checked with In Memory Read Limit of Oak Query Engine config with maximum(600000) but nothing worked for me.

I was referring below guide 

https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/troubleshooting-slow-queries.html 

Is anyone is having any idea what can be causing the issue and what can be the solution for it.

Please revert.

Thanks

Umesh Thakur

    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 joerghoh

    Are you using the Audit Log functionality of ACS AEM Commons? In that case you should raise a ticket there.

    It seems that the query you are doing is not covered by any index, and to preserve the performance of the instance, the query is terminated after 300k nodes have been traversed.

    1 reply

    joerghoh
    Adobe Employee
    joerghohAdobe EmployeeAccepted solution
    Adobe Employee
    October 1, 2020

    Are you using the Audit Log functionality of ACS AEM Commons? In that case you should raise a ticket there.

    It seems that the query you are doing is not covered by any index, and to preserve the performance of the instance, the query is terminated after 300k nodes have been traversed.

      Terms & ConditionsAccessibility statement

      Loading footer...