[SLING-4372] The use of finalize in ResourceResolver leads to performance issues

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Resource Resolver 1.1.12
• Fix Version/s: Resource Resolver 1.1.14
• Assignee: Carsten Ziegeler
• Reporter: Konrad Windszus
• Created: 30/Jan/15 08:56
• Updated: 08/Dec/16 07:06
• Resolved: 12/Feb/15 14:19

Description

Currently there is a finalizer implemented for the ResourceResolverImpl (http://svn.apache.org/repos/asf/sling/trunk/bundles/resourceresolver/src/main/java/org/apache/sling/resourceresolver/impl/ResourceResolverImpl.java).

This defers garbage collection. For a more detailed analysis and also some metrics around that have a look at https://issues.apache.org/jira/browse/JCR-2768.
A similar approach like in the patch attached to JCR-2768 should be implemented for the ResourceResolverImpl.

Issue Links

• is related to: SLING-6375 Log a warning in case a resource resolver is closed by the Sling RR Finalizer thread
• relates to: SLING-3859 ResourceResolver from JcrItemAdapterFactory is not closed
• relates to: JCR-2768 Finalize method on SessionImpl