Author going down when bulk publishing content fragments after upgrading to 6.5.17 | Community
Skip to main content
M
midhun1909
Level 2
August 14, 2023
Solved

Author going down when bulk publishing content fragments after upgrading to 6.5.17

  • August 14, 2023
  • 2 replies
  • 672 views

Hi Team,

 

We recently upgraded our AEM environments to 6.5.17 from 6.5.7 .Now when we try to bulk publish content fragments the reference.json is called and that runs for a long time bringing the instance down. Does anybody faced this issue post service pack upgrade? I see there are many UI changes with the CF publish, Save and Close options. 

 

Thanks,

Midhun

 

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 aanchal-sikka

@midhun1909 

 

There was some related to Sites "Retrieving Sites references fails on servlet. (SITES-10901)", which was fixed in 6.5.17 https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/release-notes.html?lang=en#sites-6517

 

It might be worth investigating the same. The issue that you facing with CF publishing might be related.

2 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
August 15, 2023

@midhun1909 did u try to hit the reference.json manually.. do you see anything in logs? I suspect something related to OOTB index.. try reindexing the same..

    aanchal-sikka
    Community Advisor
    aanchal-sikkaCommunity AdvisorAccepted solution
    Community Advisor
    August 15, 2023

    @midhun1909 

     

    There was some related to Sites "Retrieving Sites references fails on servlet. (SITES-10901)", which was fixed in 6.5.17 https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/release-notes.html?lang=en#sites-6517

     

    It might be worth investigating the same. The issue that you facing with CF publishing might be related.

    Aanchal Sikka
      M
      midhun1909Author
      Level 2
      August 18, 2023

      You mean to say the issue is fixed in 6.5.17?

      Terms & ConditionsAccessibility statement

      Loading footer...