AEM : org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl Unclosed ResourceResolver was created here: java.lang.Exception

Hi @udayapoornimara 
This seems similar to https://forums.adobe.com/thread/2343431 

The error you're encountering in your live environment on AEM 6.5.19, related to an unclosed ResourceResolver, is a common issue that can lead to memory leaks and performance degradation if not addressed properly. This error indicates that a ResourceResolver instance was created but not properly closed after its use. The ResourceResolver should always be closed in a finally block or using a try-with-resources statement to ensure it gets closed even if an exception occurs.

Since you're not experiencing this issue in lower environments, it might be related to specific conditions or workflows in your live environment. It could be triggered by custom code, workflows, or specific asset processing tasks that are not executed or tested in your lower environments.

To address this issue, you should:

1. Review Custom Code: Check any custom code or scripts that obtain a ResourceResolver instance, especially around the areas indicated by the stack trace (e.g., custom workflow steps, event listeners, or scheduled jobs). Ensure that every ResourceResolver is properly closed.

2. Use Try-With-Resources: For any new code or when updating existing code, use the try-with-resources statement to manage the ResourceResolver. This Java feature automatically handles the closing of resources and makes your code cleaner and safer. Here's an example pattern for using ResourceResolver within a try-with-resources statement:

   java

   try (ResourceResolver resolver = resourceResolverFactory.getServiceResourceResolver(paramMap)) { // Your code that uses the resolver here } catch (LoginException e) { // Handle potential exceptions here }

3. Investigate Workflows and Processes: Given the stack trace points to INDDMediaExtractProcess, review any custom Adobe InDesign document (INDD) media extraction processes you have. There might be an oversight in resource management within these processes.

4. Enable Resource Resolver Leak Detection: If you continue to face difficulties pinpointing the issue, consider enabling the Resource Resolver Leak Detection feature in OSGi. This can help identify where resource resolvers are not being closed. -> https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-16548

5. Audit and Test: Perform a thorough audit of your application's use of the ResourceResolver API and create unit and integration tests to ensure resource resolvers are always closed. Testing in an environment that closely mirrors your live setup can help identify issues that only occur under specific conditions.

6. Upgrade to AEM 6.5's latest Service Pack: If you find out that this exception is coming from the platform itself, please install the latest service pack, as most previous product problems are fixed and enhanced.