Sling servlet is not resolving | Community
Skip to main content
GK-007
GK-007
New Participant
October 31, 2015
Solved

Sling servlet is not resolving

  • October 31, 2015
  • 10 replies
  • 3091 views

 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

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 edubey

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

10 replies

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
New Participant
November 1, 2015

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

smacdonald2008
smacdonald2008
New Participant
October 31, 2015

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

edubey
edubeyAccepted solution
New Participant
October 31, 2015

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

GK-007
GK-007Author
New Participant
October 31, 2015

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 

O
ogill
Employee
October 31, 2015

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-007
GK-007Author
New Participant
October 31, 2015

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.

O
ogill
Employee
October 31, 2015

Is it working correctly in the Author instance?

Is the issue only in the publish instance?

GK-007
GK-007Author
New Participant
October 31, 2015

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.

O
ogill
Employee
October 31, 2015

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

edubey
edubey
New Participant
October 31, 2015

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?

Terms & ConditionsAccessibility statement

Loading footer...