I am seeing exceptions of the form:
14:26:00.241 ERROR [Apache Sling JCR Resource Event Queue Processor]
<o.a.s.j.r.i.h.jcr.JcrNodeResource> Unable to get resource type for node node
21d3300e-ea8c-46c7-9f77-5ba9880b754f
javax.jcr.InvalidItemStateException: Item does not exist anymore:
21d3300e-ea8c-46c7-9f77-5ba9880b754f
at
org.apache.jackrabbit.core.ItemImpl.itemSanityCheck(ItemImpl.java:116)
at
org.apache.jackrabbit.core.ItemImpl.sanityCheck(ItemImpl.java:104)
at
org.apache.jackrabbit.core.NodeImpl.getPrimaryNodeType(NodeImpl.java:2337)
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrItemResource.getResourceTypeForNode(JcrItemResource.java:121)
Our application receives a large batch of images and POSTs them into Sling one
at a time (thus storing them in Jackrabbit). At a later time, less than one
minute, a task runs which iterates over the Resources looking for certain
criteria. There is some navigation up and down the tree and some examining of
properties. It is at this point that I receive the exceptions as shown above. I
never see the same UUID twice; once I've received an exception I don't see a
repeat. I'm wondering if certain nodes are vanishing from my repository.
I'm at a loss to start tracking this down. I do not do any removal of nodes; my
repository should only be growing. I'm not sure what I might be doing that is
triggering this behavior.
We are using Jackrabbit 2.2.0 within Sling. Are there any known defects related
to this?
Thanks!
