Hi, We are facing some intermittent issues with one of our AEM applications that we have recently launched. We used AEM to build the frontend that has Components rendering the API data through AEM servlets, and we do have multiple users that are being managed through Cookies and third party user aut...

Thanks, Based on the requirements, we are experimenting with different TTL and when to clear the cache.

@SantoshSai sorry for the delay. Thank you for providing the code. We are calling third-party services via Models and Servlets, as well as AEM rendering.To cache the Model's and Servlet's third-party responses, we are using the Ehcache technique. 

@SantoshSai , @RajaShankar  For all C2 components on the page, I'm getting the same value. @RajaShankar I believe you are correct, however @SantoshSai  How did you come up with the various values for the same component?Could you please assist me in this issue? If possible, a sample of the model's co...

Thank you for the reference; nevertheless, the reference links are unhelpful.

@SantoshSai , Thanks for the quick response. But I am unable login to the system/console as well. same error is throwing:-URI: /system/console.STATUS: 500MESSAGE: Server ErrorSERVLET: org.apache.felix.http.base.internal.dispatch.DispatcherServlet-3a3f0585CAUSED BY: java.lang.IllegalArgumentException...

Hi,We've been dealing with this issue a lot recently. According to Adobe, the code could be corrupting the instance. However, we have had no problems with the same code being deployed in multiple instances for nearly 5 months. I cleared all cookies and opened an incognito window.The login-token appe...

Hello, in the component, I'm having trouble with Models calls. This page is taking an extremely long time to render.I've made a page with five components, let's call them C1,C2,C3,C4,C5, and we've used C2 four times and C4 ten times.The page's components are arranged in the following order: C1,C2,C2...

Robots.txt is cached at the akamai level. Akamai has updated the rules, now it is working as expected. @Anish-Sinha Thanks for the inputs.  

Apologies for the late response. We used the identical settings, but it seems to be caching someplace; we didn't find the file in the /mnt/var/www/html/content/dam/domain1/robots.txt cache folder either. We suspected that it was cached at the Akamai level, but not at the AEM level. We're collaborati...