AEM 6.4.8 en-us content publish resulted in contents deleted from a geo site by msm-service | Community
Skip to main content
A
akashdeepAEM
Level 3
July 9, 2021
Solved

AEM 6.4.8 en-us content publish resulted in contents deleted from a geo site by msm-service

  • July 9, 2021
  • 2 replies
  • 1920 views

Hi,

cc @kautuk_sahni @joerghoh  @leoberliant  @user05162 @arunpatidar 

We noticed on content (/content/proj/en-us/prod/accessories ) replication resulted in (/content/proj/ja-jp/prod/accessories) delete by msm-service from one of the many geo sites.

This section of content (/prod/accessories ) was only deleted from one of the geo site (jp-ja) and
this geo site (jp-ja) had pages which donot exists on en-us(master) but specific to this geo (jp-ja). 

We suspect that Rollout Manager tried to resolve conflict which resulted in this content delete.
as there was a com.day.cq.wcm.api.WCMException: javax.jcr.InvalidItemStateException during that time. 



... 1 line omitted ... com.day.cq.wcm.api.WCMException: javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in /content/proj/en-in/products/

accessories/jcr:content at com.day.cq.wcm.msm.impl.RolloutManagerImpl.save(RolloutManagerImpl.java:944) [com.day.cq.wcm.cq-msm-core:5.11.84] at com.day.cq.wcm.msm.impl.RolloutManagerImpl.save(RolloutManagerImpl.java:928) [com.day.cq.wcm.cq-msm-core:5.11.84] at com.day.cq.wcm.msm.impl.RolloutManagerImpl.rolloutPageRelations(RolloutManagerImpl.java:627) [com.day.cq.wcm.cq-msm-core:5.11.84] at com.day.cq.wcm.msm.impl.RolloutManagerImpl.rolloutRelations(RolloutManagerImpl.java:869) [com.day.cq.wcm.cq-msm-core:5.11.84]


Is there a recommended way to avoid this deletion?
what is the recommendation on configuring this Day CQ WCM Rollout Manager in a similar use case.

Do you think, we should increase Background thread pool size from current 5 to count of geos (25),
and increase the current max shut down time from current 10 mins to to some higher value like 30 mins ?

Thank You!

 

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

I don't think that the exception has something to do with the problem you describe. Instead it could be that this exception caused the termination of a larger operation, which would have deleted much more content.

 

What is the relation between /content/proj/en-us and /content/proj/ja-jp? Are they both livecopies from a /content/project/master tree? Or is one path the livecopy of the other path?

What Rollout Configuration have been used in the rollout?

2 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
July 13, 2021

@akashdeepaem So have you configured rollout on Publish/Activation.? Have you tried setting up "CQ MSM Content Delete Action" excluding nodetypes ?

    A
    akashdeepAEMAuthor
    Level 3
    July 13, 2021

    Hi @shashi_mulugu, thanks for replying . we have default config for CQ MSM Content Delete Action

    Are you configuring this differently

     

      joerghoh
      Adobe Employee
      joerghohAdobe EmployeeAccepted solution
      Adobe Employee
      July 18, 2021

      I don't think that the exception has something to do with the problem you describe. Instead it could be that this exception caused the termination of a larger operation, which would have deleted much more content.

       

      What is the relation between /content/proj/en-us and /content/proj/ja-jp? Are they both livecopies from a /content/project/master tree? Or is one path the livecopy of the other path?

      What Rollout Configuration have been used in the rollout?

        A
        akashdeepAEMAuthor
        Level 3
        July 20, 2021
        Hi @joerghoh,
        Terms & ConditionsAccessibility statement

        Loading footer...