"javax.jcr.nodetype.ConstraintViolationException: No matching property definition: cq:isDelivered = false" during replication | Community
Skip to main content
Level 4
October 2, 2023

"javax.jcr.nodetype.ConstraintViolationException: No matching property definition: cq:isDelivered = false" during replication

  • October 2, 2023
  • 3 replies
  • 3009 views

I'm curious what the cause of this could be. During replication we're seeing this error in our publish logs. In CRXDE Lite we show that the field "cq:isDelivered" is present. As far as I can tell we're not manipulating the JCR store in code to change this value. I'm not sure that we've changed it in the past in a way that could cause this. What am I missing?

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

3 replies

TarunKumar
Community Advisor
Community Advisor
October 3, 2023

Hi @preston-3 ,

This issue arises when some node type or property is not compatible with the node we try to save. Please double check the parent node and current node you would find some incompatible property. Remove them and replace it with the correct ones.


Thanks
Tarun

Preston-3Author
Level 4
October 3, 2023

How do you look for incompatible node types? Everything looks on the up and up in CRXDE Lite. 

TarunKumar
Community Advisor
Community Advisor
October 4, 2023

Hi @preston-3 ,

Please share the screen print of CRX node hierarchy along with the property for that specific node.

arunpatidar
Community Advisor
Community Advisor
October 3, 2023

Can you check if you are adding this by Event listerner?

the possible value could be boolean, instead of String.

Arun Patidar
Preston-3Author
Level 4
October 3, 2023

None of our custom code is adding these fields. 

arunpatidar
Community Advisor
Community Advisor
October 4, 2023

Hi @preston-3 
Can you please check creating and publishing a new page and see if you see this property for that page?

Arun Patidar
kautuk_sahni
Community Manager
Community Manager
October 4, 2023

@preston-3 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni
Preston-3Author
Level 4
October 10, 2023

Nothing here really answered this question, to be honest. We discovered while troubleshooting this that the reason content wasn't being delivered was because the queue was being blocked up by content that erroneously had a jcr:mixinType of "ReplicationStatus2". I don't know that that's related to what I was seeing here, though. Nor what caused the above. That's still outstanding, IMO.