Unable to author Experience Fragment. Throws 504 gateway error | Community
Skip to main content
B
beast08
Level 2
March 30, 2022

Unable to author Experience Fragment. Throws 504 gateway error

  • March 30, 2022
  • 4 replies
  • 2006 views

Hi,

I am on AEM 6.5 SP 7.  Whenever I am trying to author an experience fragment, I am getting below error. Using "Admin" account with full privileges.  Could not find anything in logs.. Has anyone faced this before? The content is getting updated when I refresh the page. However, the dialog is not closing on it's own and throwing timeout error with message "Fail to submit the form"

 

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

4 replies

Ritesh_Mittal
Community Advisor and Adobe Champion
Ritesh_MittalCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 30, 2022

Hi @beast08 ,

 

Please check which request is giving a timeout. You can use OSGI console (https//<IP>:<PORT>/system/console/requests) to see the recent requests. I believe from your Experience Fragment you must be calling a servlet/service which is giving a timeout.

    B
    beast08Author
    Level 2
    March 30, 2022

    Thanks for the response.

     

    It is timing out on SlingPostServlet - ModifyOperation: 

     

      Mayank_Gandhi
      Adobe Employee
      Mayank_GandhiAdobe Employee
      Adobe Employee
      March 30, 2022

      @beast08 A bit unusual issue, can you try a similar thing In another server with the same permissions? I think it's something with the instance.

        B
        beast08Author
        Level 2
        March 30, 2022

        it's working in other server. This is instance specific. 

        Not sure what's wrong. User permissions and other configurations are same.

          B
          beast08Author
          Level 2
          March 30, 2022

          We were able to fix the issue by re-indexing failing oak indexes.

           

          It was really weird that failing oak indexes were affecting experience fragment authoring. 

            Mayank_Gandhi
            Adobe Employee
            Mayank_GandhiAdobe Employee
            Adobe Employee
            March 31, 2022

            @beast08  that would have been my next suggestion, I expect a corrupted index to not stop but impact a fully working functionality. Glad you got it working!

              B
              bbitla
              December 20, 2023

              We are facing exact same issue with our experience fragments on AEM 6.5 SP18 On Premise. 

              Tried bunch of things still no resolution: 

              • Restarts - Instance and also few related bundles
              • Consistency check with came valid for all and no issues.
              • Reindexing entire repo
              • Investigated thread dumps - no sign of issues.

              Any suggestions what else can we try to fix this problem ? 

              Terms & ConditionsAccessibility statement

              Loading footer...