Sling servlet is not resolving

[GK-AEM]

 Hi All,

We have working servlet and able to use it but suddenly it is not working ,when i try to check existence of this resource using Resource Resolver from Felix Console Config manager it's not resolving.

If anyone knows the reason and what could be the resolution for this issue.

Thanks In Advance.

Thanks,

Kishore

[edubey]

It would be great if you can share the code snippet.

One more thing, as you said it suddenly stopped working, did you made any code changes, is it working once you undo code changes?

[Opkar_Gill]

Hi,

Kishore can you see your servlet in http://localhost:4502/system/console/components

Also, does the package/jar you deploy definitely have the servlet class in it?

Any errors when you are deploying to AEM in error.log?

Has someone changed the path/signature/resource type of the servlet?

Regards,

Opkar

[GK-AEM]

Opkar Gill wrote...

Hi,

Kishore can you see your servlet in http://localhost:4502/system/console/components

Also, does the package/jar you deploy definitely have the servlet class in it?

Any errors when you are deploying to AEM in error.log?

Has someone changed the path/signature/resource type of the servlet?

Regards,

Opkar

one more thing same servlet is resolving in author but same is not resolving on publisher.

i could see this servlet under the felix components section.

[Opkar_Gill]

Is it working correctly in the Author instance?

Is the issue only in the publish instance?

[GK-AEM]

Opkar Gill wrote...

Is it working correctly in the Author instance?

Is the issue only in the publish instance?

this issue only in publisher instance.

On author it's working fine.

[Opkar_Gill]

It's the same package deployed to the publish instance.

In chrome dev tools, do you see the request for the servlet? When you say it is not working, what error code is being returned to the browser.

What happens when you try to call the servlet(with parameters is required) from a browser window.

Can you check the request.log file to see what http code is returned.

[GK-AEM]

Opkar Gill wrote...

It's the same package deployed to the publish instance.

In chrome dev tools, do you see the request for the servlet? When you say it is not working, what error code is being returned to the browser.

What happens when you try to call the servlet(with parameters is required) from a browser window.

Can you check the request.log file to see what http code is returned.

same package only deployed on publisher side as well.

I am seeing 404 response when requesting for this servlet.

Getting below message when requesting with required parameters.

 No resource found

RequestURI=/apps/elibrary/servlets/SABAConnectionServlet

Servlet= /apps/sling/servlet/errorhandler/404.html 

[edubey · Accepted solution]

Hi,

can you please check crxde logs when you are installing package in publish instance. you should be able to see your servlet in logs

[smacdonald2008]

As a test  try changing the path and redeploy. Let us know if that hit the servlet with new path.

[Lokesh_Shivalingaiah]

One of your reference would not be working and hence their might be an issue. Can you post the error log ?