You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Julian Sedding (JIRA)" <ji...@apache.org> on 2017/12/14 15:35:00 UTC

[jira] [Created] (SLING-7313) ResourceResolverImpl#refresh should also refresh the internal resourceTyperesourceResolver

Julian Sedding created SLING-7313:
-------------------------------------

             Summary: ResourceResolverImpl#refresh should also refresh the internal resourceTyperesourceResolver
                 Key: SLING-7313
                 URL: https://issues.apache.org/jira/browse/SLING-7313
             Project: Sling
          Issue Type: Improvement
          Components: ResourceResolver
    Affects Versions: Resource Resolver 1.5.32
            Reporter: Julian Sedding
            Priority: Minor
         Attachments: refresh-session.txt

I noticed warning log messages due to long-lived Oak sessions (see attachment) and traced them back to a long-lived service {{ResourceResolver}} in the I18N code ({{JcrResourceBundleProvider}}). Care is taken to periodically refresh this {{ResourceResolver}}, however, the {{#refresh()}} call is not propagated to the internal {{resourceTypeResourceResolver}} used by {{ResourceResolverImpl}} and thus a warning is logged.

This could be solved by using short-lived RRs in the I18N code, but I think we should also refresh the internal {{resourceTypeResourceResolver}} used by {{ResourceResolverImpl}} when RR is refreshed.





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)