Jörg Hoh created SLING-6104:
-------------------------------
Summary: Improve handling to avoid Oak warning
Key: SLING-6104
URL: https://issues.apache.org/jira/browse/SLING-6104
Project: Sling
Issue Type: Improvement
Components: Installer, JCR
Affects Versions: JCR Installer 3.1.16, JCR Resource 2.8.0, Pipes 0.0.10
Reporter: Jörg Hoh
I often see messages like this in our logs (AEM 6.0):
{noformat}
WARN org.apache.jackrabbit.oak.jcr.session.ItemImpl Item#refresh invokes
Session#refresh!
{noformat}
I found that in
bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/JcrResourceUtil.java
there is one occurrences of this pattern:
{code}
444 } catch (RepositoryException re) {
445 // we ignore this as this folder might be
created from a different task
446 node.refresh(false);
447 }
{code}
This should be changed to {code}node.getSession().refresh(false);{code} to
avoid this warning. From my point of view the semantic does not change.
I found the same pattern here as well:
*
installer/providers/jcr/src/main/java/org/apache/sling/installer/provider/jcr/impl/JcrUtil.java
*
contrib/extensions/sling-pipes/src/main/java/org/apache/sling/pipes/PathPipe.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
