[
https://issues.apache.org/jira/browse/SLING-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15554382#comment-15554382
]
Carsten Ziegeler commented on SLING-6104:
-----------------------------------------
Fixed jcr.resource in rev 1763684
> 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 Resource 2.8.0, JCR Installer 3.1.16, Pipes 0.0.10
> Reporter: Jörg Hoh
> Fix For: JCR Resource 2.8.2, JCR Installer 3.1.18, Pipes 0.0.10
>
>
> 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)
