AEM 6.4 Uncaught SlingException (No custom code) | Community
Skip to main content
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 vijkumar

In such a scenario the previous request is aborted and the error [1] is logged depicting that the very same request is triggered again so aborting the previous one.

That being said, this should not cause any issue to the functionality as the final/last request will succeed and the result for the request would be displayed on the UI successfully. In your scenario even if you trigger multiple different internal requests on the same page, this would not be a concern as this happens only when the very same request is triggered again and not if the requests are different.

Note: These logs are not harmful and would not cause any functionality to break. These are just to log the abort of the previous requests from the Host machine(browser).

1 reply

vijkumar
Adobe Employee
vijkumarAdobe EmployeeAccepted solution
Adobe Employee
June 20, 2019

In such a scenario the previous request is aborted and the error [1] is logged depicting that the very same request is triggered again so aborting the previous one.

That being said, this should not cause any issue to the functionality as the final/last request will succeed and the result for the request would be displayed on the UI successfully. In your scenario even if you trigger multiple different internal requests on the same page, this would not be a concern as this happens only when the very same request is triggered again and not if the requests are different.

Note: These logs are not harmful and would not cause any functionality to break. These are just to log the abort of the previous requests from the Host machine(browser).

    Terms & ConditionsAccessibility statement

    Loading footer...