javax.jcr.nodetype.ConstraintViolationException: No default node type available | Community
Skip to main content
varshneyanuj
Level 2
November 3, 2016

javax.jcr.nodetype.ConstraintViolationException: No default node type available

  • November 3, 2016
  • 1 reply
  • 2552 views

Hi,

Recently we have migrated to AEM 6.2. We get below error when we try to invoke workflow to publish Asset. The workflow works fine in case of sites.

We have custom workflows to publish the content but in this case (Assets), the workflow doesn't get invoked and we get below error. No error reported at Workflow console.

 

02.11.2016 10:57:01.312 *ERROR* [10.1.51.107 [1478105821307] POST /assets.html/content/dam HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation Unable to create resource named dam in /libs/dam/gui/content/assets/content
02.11.2016 10:57:01.312 *ERROR* [10.1.51.107 [1478105821307] POST /assets.html/content/dam HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation Exception during response processing.
javax.jcr.nodetype.ConstraintViolationException: No default node type available for /libs/dam/gui/content/assets/content/dam
        at org.apache.jackrabbit.oak.util.TreeUtil.addChild(TreeUtil.java:185)
        at org.apache.jackrabbit.oak.jcr.delegate.NodeDelegate.addChild(NodeDelegate.java:693)
        at org.apache.jackrabbit.oak.jcr.session.NodeImpl$5.perform(NodeImpl.java:297)
        at org.apache.jackrabbit.oak.jcr.session.NodeImpl$5.perform(NodeImpl.java:263)
        at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:208)
        at org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
        at org.apache.jackrabbit.oak.jcr.session.NodeImpl.addNode(NodeImpl.java:263)
        at org.apache.jackrabbit.oak.jcr.session.NodeImpl.addNode(NodeImpl.java:248)

 

Any pointers?

Thanks in advance!

-Anuj Varshney

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

1 reply

smacdonald2008
Level 10
November 3, 2016

Where are you publishing your assets. In the message it states:

Unable to create resource named dam in /libs/dam/gui/content/assets/content

varshneyanuj
Level 2
November 4, 2016

To publish instance... Yeah, not sure from where its picking that location.

Thanks

Anuj Varshney

smacdonald2008
Level 10
November 4, 2016

This looks like some sort of bug - it should publish - open a ticket and see if a hotfix is required.