You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "prestoncrawford (via GitHub)" <gi...@apache.org> on 2024/01/12 20:19:54 UTC

Re: [PR] JCRVLT-737 failing testcase [jackrabbit-filevault]

prestoncrawford commented on PR #326:
URL: https://github.com/apache/jackrabbit-filevault/pull/326#issuecomment-1889899936

   @joerghoh - We're seeing this "Parent node not found" error in our AEMaaCS instances periodically while replicating assets. The only common denominator that I can determine so far is that the assets that fail this way have a custom nodeType that doesn't exist on the Publish instance. 
   
   In our case we have assets that have a `jcr:mixinType` of "cq:ReplicationStatus2". When I try to recreate this error in a local environment using a local Author and Publish environment generated using AEMaaCS jars the error presents itself like this. 
   
   "2024-01-12 11:34:11 - ERROR - publish : << error: com.day.cq.replication.ReplicationException: Repository error during node import: Node type cq:ReplicationStatus2 is not a mixin type"
   
   We've been banging our heads against the wall. Am I reading correctly that you've identified the cause of the "parent node not found" to be the existence of custom nodeTypes? Does our error sound similar to this? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@jackrabbit.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org