Konrad Windszus created OAK-7591:
------------------------------------

             Summary: Expose the node name for CommitFailedException
                 Key: OAK-7591
                 URL: https://issues.apache.org/jira/browse/OAK-7591
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: core
    Affects Versions: 1.9.4
            Reporter: Konrad Windszus


Currently the exception messages for a {{CommitFailedException}} is pretty 
generic. E.g. I have seen something like this being thrown for a 
{{Session.save()}} containing changes on 1024 nodes:

{code}
javax.jcr.version.VersionException: OakVersion0001: Cannot change property 
jcr:mixinTypes on checked in node
        at 
org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:241)
        at 
org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:212)
        at 
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.newRepositoryException(SessionDelegate.java:670)
        at 
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.save(SessionDelegate.java:496)
        at 
org.apache.jackrabbit.oak.jcr.session.SessionImpl$8.performVoid(SessionImpl.java:419)
        at 
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.performVoid(SessionDelegate.java:274)
        at 
org.apache.jackrabbit.oak.jcr.session.SessionImpl.save(SessionImpl.java:416)
        at 
com.adobe.granite.repository.impl.CRX3SessionImpl.save(CRX3SessionImpl.java:208)
        at 
...
 Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: 
OakVersion0001: Cannot change property jcr:mixinTypes on checked in node
        at 
org.apache.jackrabbit.oak.plugins.version.VersionEditor.throwCheckedIn(VersionEditor.java:250)
        at 
org.apache.jackrabbit.oak.plugins.version.VersionEditor.propertyChanged(VersionEditor.java:131)
{code}

It would be helpful to at least include the conflicting node path in the 
exception message, to ease debugging.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to