IllegalStateException: Parent node not found while publishing content fragment | Community
Skip to main content
P
Preston-3
October 3, 2023

IllegalStateException: Parent node not found while publishing content fragment

  • October 3, 2023
  • 2 replies
  • 1359 views

In attempting to publish content fragments there are a couple of pieces of content that cause the replication queue to be blocked with this error. 


Caused by: org.apache.jackrabbit.vault.packaging.PackageException: Error creating/updating node /content/dam/.../jcr:content at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1104) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:905) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:945) at org.apache.jackrabbit.vault.fs.io.Importer.run(Importer.java:511) ... 12 more

Caused by: java.lang.IllegalStateException: Parent node not found. at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1030) ... 24 more

Any idea what could cause this? The parent node would be the parent node of the content fragment, right? Other sibling content fragments publish fine. 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

DPrakashRaj
Community Advisor
DPrakashRajCommunity Advisor
Community Advisor
October 4, 2023

Can you check if parent node is present as during publishing it will try to add/update some jcr properties so looks for the complaining node in your crx/de

    P
    Preston-3Author
    October 4, 2023

    It's definitely there. Yesterday as a test I duplicated the content fragment itself, deleted the old one, then renamed the duplicate content fragment to be the same as the original one. That one published without issue. So it has to be something else, like a permissions issue or some setting that isn't visible in CRXDE Lite.

      N
      naveen_27_05
      February 14, 2024

      You need to check two scenarios here.

      1. Check whether the parent node is published or not. if the parent node is not published we get these errors.

      2. Check if any special characters are there in the node. 

      Terms & ConditionsAccessibility statement

      Loading footer...