Adobe Experience Manager Sites & More

ashishm85330433 · 2/7/24

Hi All,

Can anyone please suggest me what is the best way to resolve AEM production issue when using on Prem environment.?

Any product issue example will be great to understand the approach so that I can help my team

aanchal-sikka · 2/8/24

@ashishm85330433

How you should debug depends on what your issue is? You might need to be more specific about what issue you are facing.

Please refer to this KB Article, which discusses issue, reasons, debugging and solution on:

Memory
performance
Indexing
Replication

https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-17457.html?lang=en

For debugging caching, refer to: https://techrevelhub.wordpress.com/2023/09/05/exploring-aem-request-and-response-headers-analysis-of...

For 500 errors, check AEM logs.

Aanchal Sikka

View solution in original post

SureshDhulipudi · 2/7/24

General Troubleshooting or Debug Any Issue:

Are you able to reproduce or replicate the same issue in Lower DEV environment
Reproducible in Local AEM environment
Debug Loggers / Headers (Author / Publish / Dispatcher )
Is the issue with Content ?
Is the issue with Caching ? (Cache clear resolve the issue?)
If the issue with CODE - keep Logger statements and check the ERROR Logs
Enable Debug Logging: If the error logs do not provide enough information, you can enable debug logging for specific packages in AEM. This can be done via the OSGi Web Console

Based on above different scenarios will help in debugging any issue.

If issue is related with Code - You can used IDE and Run AEM instance in Debug mode and keep break points.

partyush · 2/7/24

Hi @ashishm85330433

The best way to resolve AEM production issues in an on-premises environment involves a structured approach tailored to the specific problem at hand. Here's a step-by-step guide:

Identify the Issue: Gather detailed information about the problem, including symptoms, error messages, affected functionality, and any recent changes made to the environment.
Check Logs: Review AEM logs, including error logs, access logs, and dispatcher logs, to identify any relevant information that may help diagnose the issue.
Use AEM Health Checks: Leverage AEM's built-in health checks to identify common issues, misconfigurations, or performance bottlenecks within the environment.
Replicate the Issue: Attempt to replicate the problem in a controlled environment, such as a staging or development environment, to isolate the root cause and test potential solutions without impacting production.
Review Recent Changes: Investigate any recent changes or deployments made to the AEM environment, including code changes, configuration updates, or content modifications, which may have introduced the issue.
Engage Support Channels: If unable to resolve the issue internally, engage support channels such as Adobe Support or consult with AEM experts for additional assistance and guidance.
Apply Hotfixes and Patches: Check for available hotfixes or patches provided by Adobe or third-party vendors to address known issues or vulnerabilities in AEM and apply them as necessary.
Monitor and Test: After implementing a solution, closely monitor the AEM environment to ensure that the issue has been resolved and conduct thorough testing to verify that the affected functionality is working as expected.

For example, if users are experiencing slow page load times on a production AEM website, the resolution process might involve identifying performance bottlenecks, analyzing server metrics, optimizing caching configurations, and applying performance-related hotfixes or patches provided by Adobe.

By following this structured approach, you can efficiently diagnose and resolve production issues in your AEM environment while minimizing downtime and ensuring a seamless user experience for your website visitors.

Thanks

ashishm85330433 · 2/16/24

Thanks Partyush

Raja_Reddy · 2/7/24

Hi @ashishm85330433
Some general steps that you can follow :

Identify the issue: Review logs and user reports to identify the issue. In this case, users are reporting that they are unable to access a specific page on the website.
Reproduce the issue: Try to reproduce the issue in a test environment. In this case, try to access the page in the test environment to see if the issue can be reproduced.
Analyze the issue: Review logs and configurations to determine the root cause of the issue. In this case, review the access logs and configurations for the page to determine if there are any issues.
Develop a solution: Once you have identified the root cause of the issue, develop a solution. This can involve making changes to code, configurations, or infrastructure. In this case, the issue may be caused by a misconfiguration in the dispatcher configuration file.
Deploy the solution: Once you have tested the solution, deploy it to production. Follow a structured deployment process to ensure that the solution is deployed correctly and does not cause any additional issues.
Verify the solution: Once the solution is deployed, verify that the issue has been resolved. In this case, test the page to ensure that users can access it without any issues.

kautuk_sahni · 2/8/24

@ashishm85330433 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.