Hey,I didn't get the part of version purging with Oak jar. May be something I don't know.....But, you can do the version purging using the Purge tool available with in AEM. http://<server>:<port>/etc/versioning/purge.htmlAlso, as described in above comment, please make sure to create purge configura...

The easiest way, please debug the code by breaking into multiple statements and check if the value exist in valuemap or not. Resource contentRes =  page.getContentResource();ValueMap map =  contentRes.getValueMap();String templatePath =  map.get("cq:template").toString();Put the null check and add d...

Hi,Please follow the link: https://www.aemquickstart.in/2016/12/configure-dispatcher-for-aem.html Make sure you've all the configuration correct. Check port number specifically and Webserver cache directory and /docroot path should be same.

Please check your dispatcher logs and make sure that AEM Dispatcher settings are correct. Or if you're getting any specific error, please share it...

Let's say in a page I've 10 components and out of which one component backend logic doesn't work as expected and throws null pointer exception. In that case, it breaks the rendering of whole page yet the page status it displays is 200 which is not okay.So, if there's any 500 error occurs due to (I m...

The code snippet is the same as I shared in question post. The problem is that when the component logic is invoked(the one which throws error), before that there are other components sling models are called and some of it are writing the JSON response back on page and also setting up the cookies.Cou...

And, I think I understand the problem why it's not working for 500. For the 404, since the resource doesn't exist, in that case, it doesn't make any call to any of AEM resource and hence directly jump to error handler and render the error page (could be via include, forward or sendRedirect - all wor...

Errata; It‘s "Response already committed"

Changing the size doesn't help. And, also, tried ACS commons way - with that one also getting the "Response not committed" for 500 error.

Nope; It's something AEM internal 'cos at multiple places let's say null check is not there so it throws 500 error.