[
https://issues.apache.org/jira/browse/SLING-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-2366.
--------------------------------------
Resolution: Fixed
Reduced logging to debug level -- such situations may happen, e.g. due to ACL
restrictions or for temporary nodes already removed again.
Therefore, adding a refresh does not help much and I did not add it.
> JcrResourceListener: May log many errors, which are not really errors
> ---------------------------------------------------------------------
>
> Key: SLING-2366
> URL: https://issues.apache.org/jira/browse/SLING-2366
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.10
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.1.0
>
>
> When preparing OSGi Events the JcrResourceListener tries to access the
> resource which triggered the event. This may in some cases return a null
> resource (because the session is not current or because the resource has
> already been removed again because it is a short lived resource). Currently
> such a situation is logged as an error, which is of course not appropriate.
> Instead we just log a debug message (to at least be able to track this in
> case of problems).
> Also we might retry getting the resource after refreshing the session.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
