Magnolia

update: update fails with a ConstraintViolationException if workflows are in progress

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Workaround exists
  • Affects Version/s: 3.5.2
  • Fix Version/s: 3.5.3
  • Component/s: None
  • Labels:
  • Description:
    Hide

    Could not perform installation: javax.jcr.nodetype.ConstraintViolationException: /owfe/activation/1196324976061.0/0.1.0__loop: mandatory child node {}MetaData does not exist
    at org.apache.jackrabbit.core.ItemImpl.validateTransientItems(ItemImpl.j
    ava:549)

    Show
    Could not perform installation: javax.jcr.nodetype.ConstraintViolationException: /owfe/activation/1196324976061.0/0.1.0__loop: mandatory child node {}MetaData does not exist at org.apache.jackrabbit.core.ItemImpl.validateTransientItems(ItemImpl.j ava:549)
  1. custom_nodetypes.xml
    (7 kB)
    Philipp Bracher [old account - now Philipp Bärfuss]
    21/Dec/07 11:14 AM

Activity

Hide
Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 21/Dec/07 11:13 AM

To fix that you have to replace the file repositories/magnolia/repository/nodetypes/custom_nodetypes.xml before you start updating with the one of 3.5

Show
Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 21/Dec/07 11:13 AM To fix that you have to replace the file repositories/magnolia/repository/nodetypes/custom_nodetypes.xml before you start updating with the one of 3.5
Hide
Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 21/Dec/07 11:14 AM

You can use the attached file

Show
Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 21/Dec/07 11:14 AM You can use the attached file
Hide
Vivian Steller added a comment - 10/Jan/08 4:07 PM

this only happens when updating from a version pre-3.0.2 (maybe transiently, if you updated 3.0.1 > (ok) > 3.0.2 > (crash) > 3.5).

some more detailed explanation: 3.0.1 had a nodetype definition of the expression node in place that sais "metaData is mandatory" (see owfe-nodetypes.xml in workflow module). This nodetype definition is copied to the repositories/magnolia/repository/nodetypes/custom_nodetypes.xml file when installing 3.0.1. When updating this instance to 3.5 (by either replacing jars or copying the repository to a newly created instance) an update task of 3.5 removes the metadata node. Since you then still have the original custom_nodetypes.xml file in place Jackrabbit complains with the exception above.

As mentioned before, fix this by adjusting the appropriate expression nodetype in custom_nodetypes.xml or just replace the whole file with the one attached entirely.

Show
Vivian Steller added a comment - 10/Jan/08 4:07 PM this only happens when updating from a version pre-3.0.2 (maybe transiently, if you updated 3.0.1 > (ok) > 3.0.2 > (crash) > 3.5). some more detailed explanation: 3.0.1 had a nodetype definition of the expression node in place that sais "metaData is mandatory" (see owfe-nodetypes.xml in workflow module). This nodetype definition is copied to the repositories/magnolia/repository/nodetypes/custom_nodetypes.xml file when installing 3.0.1. When updating this instance to 3.5 (by either replacing jars or copying the repository to a newly created instance) an update task of 3.5 removes the metadata node. Since you then still have the original custom_nodetypes.xml file in place Jackrabbit complains with the exception above. As mentioned before, fix this by adjusting the appropriate expression nodetype in custom_nodetypes.xml or just replace the whole file with the one attached entirely.

People

Dates

  • Created:
    21/Dec/07 11:11 AM
    Updated:
    17/Mar/09 7:48 PM
    Resolved:
    10/Jan/08 4:07 PM