500 Internal Server Error - AEM dispatcher instance

[sonaliku]

We have a headless implementation where an external application calls our servlets in bulk (1000s requests) at the same time. We are running into Internal server 500 error for a bulk of these dispatcher requests although they technically should be 200 Valid Responses. Any inputs on this issue would be helpful.

[EstebanBustamante]

A 500 error means something went wrong in your application logic. You need to check the logs to understand where the issue occurred.

Check if you are able to directly access the Publish instance to understand if the error occurs in the AEM server or Dispatcher layer. Then, check the logs accordingly.

Hope this helps.

[sherinregi · Accepted solution]

500 Internal server error comes from application and the dispatcher will send the response what it received from the publishers. As you have mentioned you are receiving bulk request at the same time if the responses are not cached it will hit the publishers every time and if there is  an error/issue in publish logs it will throw 500. You need to check this on publish logs and once this is resolved your publisher will be able to handle the requests .

 Also try to hit the requests individually and see if it returns 200 so in that case you can slowly increase the load and see the threshold and optimize 

[kautuk_sahni]

@sonaliku Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.