Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

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

Anonymous
Not applicable

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:

image001.png

1 Accepted Solution
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

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.

View solution in original post

4 Replies
smacdonald2008
Level 10
Level 10

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

Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

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.

View solution in original post

Veena_Vikram
Community Advisor
Community Advisor

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

BattiniSravan
Level 2
Level 2

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