AEM 6.3 - Requested Path *.servlet is not in available search paths / 500 Server Error | Community
Skip to main content
A
Anonymous
September 21, 2018
Solved

AEM 6.3 - Requested Path *.servlet is not in available search paths / 500 Server Error

  • September 21, 2018
  • 4 replies
  • 6672 views

We had some services work properly but after a server restart we are seeing a bank response  / 500 Server Error .

Not sure what is wrong? Appreciate any help!

Error message in logs are like: Requested Path /bin/sirius/report.servlet is not in available search paths for any custom service we developed.

Snippet form logs:

21.09.2018 10:52:30.448 *WARN* [192.150.10.209 [1537541550444] POST /bin/sirius/report HTTP/1.1] com.day.cq.wcm.core.impl.components.ComponentCacheImpl Requested Path /bin/sirius/report.servlet is not in available search paths

Sling Servlet Resolver shows the correct class:

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 arunpatidar

Hi,

Your servlet looks ok but another dependent servlet/service (/bin/sirius/report) have some issue, better to check that service if this service/bundle is up or not.

And your making POST call, check for apache sling referrer filter config as well for POST calls.

4 replies

smacdonald2008
smacdonald2008
Level 10
September 27, 2018

Is the OSGi servlet that defines this Sling Servlet in an Active State?

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
September 27, 2018

Hi,

Your servlet looks ok but another dependent servlet/service (/bin/sirius/report) have some issue, better to check that service if this service/bundle is up or not.

And your making POST call, check for apache sling referrer filter config as well for POST calls.

Arun Patidar
VeenaVikraman
Community Advisor
VeenaVikramanCommunity Advisor
Community Advisor
September 27, 2018

Can you give the screenshot of your service ? is it active ?

B_Sravan
Community Advisor
B_SravanCommunity Advisor
Community Advisor
November 23, 2021

looks like it need changes to "sling referrer filter config" and "adobe granite CSRF Filter". Configure them by removing the POST method. After making configurations to the two OSGI configurations, you should be able to make a POST request from your HTTP REST Client to your AEM instance.

For production, set Apache Sling Referrer Filter and Adobe Granite CSRF Filter settings back to default. Unless if you are giving access to other servers to make POST requests to your AEM application.

reference: https://sourcedcode.com/blog/aem/how-to-make-simple-http-post-methods-in-aem-with-a-http-rest-client 

Terms & ConditionsAccessibility statement

Loading footer...