Details
-
Bug
-
Resolution: Obsolete
-
Neutral
-
None
-
None
-
None
-
Empty show more show less
-
Pages Maintenance 3, Pages Maintenance 4
-
3
Description
Steps to reproduce
- Create page with multiple variants
- Configure activation command for personalization to also include mgnl:variant
- Publish the page
Expected results
- Page is published including variants
Actual results
- Errors related to the variant observation mechanism appear
2021-02-19 13:55:39,227 ERROR registry.variant.ConfiguredVariantObservingManager: Unable to create variant provider from variant node [node /Emocion/variants/variant-2/cuerpo/0111110] javax.jcr.InvalidItemStateException: Item does not exist anymore: 0125efa3-94c9-41e2-91cf-d6e18318ba44 at org.apache.jackrabbit.core.ItemImpl.itemSanityCheck(ItemImpl.java:116) ~[jackrabbit-core-2.18.1.jar:2.18.1] at org.apache.jackrabbit.core.ItemImpl.sanityCheck(ItemImpl.java:104) ~[jackrabbit-core-2.18.1.jar:2.18.1] at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2279) ~[jackrabbit-core-2.18.1.jar:2.18.1] at info.magnolia.personalization.variant.BaseVariantManager.getAllVariants(BaseVariantManager.java:70) ~[magnolia-personalization-integration-1.6.3.jar:?] at info.magnolia.personalization.registry.variant.ConfiguredVariantsProvider.<init>(ConfiguredVariantsProvider.java:48) ~[magnolia-personalization-integration-1.6.3.jar:?] at info.magnolia.personalization.registry.variant.ConfiguredVariantObservingManager.createProvider(ConfiguredVariantObservingManager.java:76) [magnolia-personalization-integration-1.6.3.jar:?] at info.magnolia.personalization.registry.variant.ConfiguredVariantObservingManager.reload(ConfiguredVariantObservingManager.java:66) [magnolia-personalization-integration-1.6.3.jar:?] at info.magnolia.cms.util.WorkspaceObservingManager$1$1.doExec(WorkspaceObservingManager.java:129) [magnolia-core-5.7.8.jar:?]
Workaround
- Do not publish with mgnl:variant rule
- Programatically increase delay and maxDelay on the ConfiguredVariantObservingManager
Development notes
This behavior happens because publication is removing nodes on pages and variants, and the observation mechanism kicks in and BaseVariantManager runs into InvalidItemStateException of some nodes because it's session is not aware of the changes made by publishing.
Checklists
Acceptance criteria
Attachments
Issue Links
- mentioned in
-
Page Loading...