"No resource found" when accessed pages with dispatcher | Community
Skip to main content
kishore_polsani
Level 4
October 25, 2017
Solved

"No resource found" when accessed pages with dispatcher

  • October 25, 2017
  • 3 replies
  • 10972 views

Hi All,

We have recently performed in-place upgrade from AEM 6.1 to AEM 6.2. We are able to access pages (/content/kishore/en/test.html) with publisher, when I try to access page (/kishore/en/test.html) with dispatcher shortened URL, we are getting 404 errror. This shortened URL was working in AEM 6.1 version.

Error Message:

25.10.2017 06:56:28.392 *INFO* [10.204.139.61 [1508914588391] GET /kishore/en/test.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /kishore/en/test.html not found

25.10.2017 06:56:28.392 *INFO* [10.204.139.61 [1508914588391] GET /kishore/en/test.html HTTP/1.1] apps.sling.servlet.errorhandler.404$jsp 404:: Starting to work with: /kishore/en/test.html

25.10.2017 06:56:28.392 *INFO* [10.204.139.61 [1508914588391] GET /kishore/en/test.html HTTP/1.1] apps.sling.servlet.errorhandler.404$jsp 404:: Resource returned for current URL. Finding a 404 page in following content structure: /kishore/en/test.html

I have checked below options

  • anonymous user has access read access.
  • Default paths (resource.resolver.searchpath) are available in "Apache Sling Resource Resolver Factory" OSGI config. Is anything changed in AEM 6.2.
  • No dispatcher rules have been updated.

Any idea what am I missing here?

Thanks,

Kishore

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

3 replies

VeenaVikraman
Community Advisor
Community Advisor
October 25, 2017

so how are you setting up those shortened urls ? is it mapping or rewrite rules ?

smacdonald2008
Level 10
October 25, 2017

This could be some sort of upgrade bug - do you have a fresh AEM instance to test with?

kishore_polsani
kishore_polsaniAuthorAccepted solution
Level 4
October 27, 2017