Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
Description
[INFO] 07.11.2013 18:39:28 ERROR pool-2-thread-1 [Exporter.exportContentResource:142] Exporting content/documents/rcclbecm/port.xml failed.
javax.jcr.PathNotFoundException: /content/documents/rcclbecm/port/northern-europe/test/test[2]
at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:552)
at org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:97)
at org.apache.jackrabbit.core.session.SessionItemOperation$4.perform(SessionItemOperation.java:93)
at org.apache.jackrabbit.core.session.SessionItemOperation.perform(SessionItemOperation.java:187)
at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:200)
at org.apache.jackrabbit.core.SessionImpl.perform(SessionImpl.java:359)
at org.apache.jackrabbit.core.SessionImpl.getItem(SessionImpl.java:747)
at org.hippoecm.repository.decorating.SessionDecorator.getItem(SessionDecorator.java:178)
at org.hippoecm.repository.impl.SessionDecorator.exportDereferencedView(SessionDecorator.java:225)
at org.onehippo.cms7.autoexport.Exporter.exportInstruction(Exporter.java:185)
at org.onehippo.cms7.autoexport.Exporter.exportInstruction(Exporter.java:201)
at org.onehippo.cms7.autoexport.Exporter.exportInstruction(Exporter.java:201)
at org.onehippo.cms7.autoexport.Exporter.exportInstruction(Exporter.java:201)
at org.onehippo.cms7.autoexport.Exporter.exportDeltaXML(Exporter.java:172)
at org.onehippo.cms7.autoexport.Exporter.exportContentResource(Exporter.java:135)
at org.onehippo.cms7.autoexport.Exporter.export(Exporter.java:110)
at org.onehippo.cms7.autoexport.Exporter.export(Exporter.java:103)
Errors like this can always happen when a concurrent thread is making changes to nodes that are read simultaneously by another thread. CMS version 7.8 still relies on this awkward carousel of document variants that are constantly created and deleted again, causing such occurrences to be more likely. Fortunately we fixed this in the 7.9. In the meantime, we could implement a retry-on-first-failure strategy for error situations like this.