Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-14794

Fix tree publishing with custom versioning rules

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.9.4
    • Fix Version/s: 5.9.5
    • Component/s: Publishing

      Description

      If a custom versioning with minor increment as default behavior is configured for a Folderish document, publishing this document will fail with the following stacktrace

      ERROR [http-bio-0.0.0.0-8080-exec-11] [javax.enterprise.resource.webcontainer.jsf.application] org.nuxeo.ecm.core.api.ClientException: Failed to check in document 24fbaa09-f6df-4de9-b5a8-d44e492a5614
      javax.faces.el.EvaluationException: org.nuxeo.ecm.core.api.ClientException: Failed to check in document 24fbaa09-f6df-4de9-b5a8-d44e492a5614
      ...
      Caused by: org.nuxeo.ecm.core.api.ClientException: Failed to check in document 24fbaa09-f6df-4de9-b5a8-d44e492a5614
              at org.nuxeo.ecm.core.api.AbstractSession.checkIn(AbstractSession.java:2032)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:606)
              at org.nuxeo.ecm.core.api.TransactionalCoreSessionWrapper.invoke(TransactionalCoreSessionWrapper.java:131)
              at com.sun.proxy.$Proxy101.checkIn(Unknown Source)
              at org.nuxeo.snapshot.SnapshotableAdapter.createLeafVersion(SnapshotableAdapter.java:96)
              at org.nuxeo.snapshot.SnapshotableAdapter.createLeafVersionAndFetch(SnapshotableAdapter.java:102)
              at org.nuxeo.snapshot.SnapshotableAdapter.createSnapshot(SnapshotableAdapter.java:184)
              at org.nuxeo.snapshot.pub.FolderishProxyFactory.publishDocument(FolderishProxyFactory.java:49)
              at org.nuxeo.ecm.platform.publisher.api.AbstractBasePublicationTree.publish(AbstractBasePublicationTree.java:126)
              at org.nuxeo.ecm.platform.publisher.impl.core.SectionPublicationTree.publish(SectionPublicationTree.java:123)
              at org.nuxeo.ecm.platform.publisher.impl.service.PublisherServiceImpl.publish(PublisherServiceImpl.java:438)
              at org.nuxeo.ecm.platform.publisher.impl.service.AbstractRemotableTree.publish(AbstractRemotableTree.java:77)
              at org.nuxeo.ecm.platform.publisher.web.PublishActionsBean.doPublish(PublishActionsBean.java:227)
              at org.nuxeo.ecm.platform.publisher.web.PublishActionsBean.doPublish(PublishActionsBean.java:214)
      
      ...
      Caused by: org.nuxeo.ecm.core.api.DocumentException: org.nuxeo.ecm.core.storage.StorageException: Already checked in
              at org.nuxeo.ecm.core.storage.sql.coremodel.SQLSession.checkIn(SQLSession.java:846)
              at org.nuxeo.ecm.core.storage.sql.coremodel.SQLDocumentLive.checkIn(SQLDocumentLive.java:366)
              at org.nuxeo.ecm.core.versioning.StandardVersioningService.doCheckIn(StandardVersioningService.java:321)
              at org.nuxeo.ecm.core.versioning.VersioningComponent.doCheckIn(VersioningComponent.java:231)
              at org.nuxeo.ecm.core.api.AbstractSession.checkIn(AbstractSession.java:2021)
              ... 134 more
      Caused by: org.nuxeo.ecm.core.storage.StorageException: Already checked in
              at org.nuxeo.ecm.core.storage.sql.PersistenceContext.checkIn(PersistenceContext.java:1471)
              at org.nuxeo.ecm.core.storage.sql.SessionImpl.checkIn(SessionImpl.java:1110)
              at org.nuxeo.ecm.core.storage.sql.ra.ConnectionImpl.checkIn(ConnectionImpl.java:290)
              at org.nuxeo.ecm.core.storage.sql.coremodel.SQLSession.checkIn(SQLSession.java:843)
              ... 138 more
      

      The publishing process tries to check in the target document whereas a previous save has forced the check in, because of the default minor increment in the versioning rules.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: