Why would a published page give a 504 after a deployment that didn't affect that page | Community
Skip to main content
S
SebNamek
Level 2
November 3, 2020
Solved

Why would a published page give a 504 after a deployment that didn't affect that page

  • November 3, 2020
  • 2 replies
  • 3327 views

I made a change to our offers page and deployed that, after that was done our help page is now throwing a 504.

I looked into the error logs and haven't seen anything. The author instance works fine. I tried republishing and that doesn't work either.

 

Just seems as if the data won't make it to the publish instance. Why did this happen and how can I fix it?

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 kiranparab

Is this page really published to your publishers ? Please validate parallel pages too if it respond correctly

 

Issues like -

1. Publishing not happened to all publishers through your replication agents. Validate the Outbox for Author instance.

2. Cached the page on dispatcher level which didnot remove the cache after activation

3. One of the publisher faulty to responed with 504 for Timeout error code.

 

2 replies

K
kiranparabAccepted solution
Level 3
November 3, 2020

Is this page really published to your publishers ? Please validate parallel pages too if it respond correctly

 

Issues like -

1. Publishing not happened to all publishers through your replication agents. Validate the Outbox for Author instance.

2. Cached the page on dispatcher level which didnot remove the cache after activation

3. One of the publisher faulty to responed with 504 for Timeout error code.

 

    K
    kiranparab
    Level 3
    November 3, 2020

    1. What is the author outbox and how can I validate that?

    -> You can validate if there is any issue in activation of the page

    -> You can validate the outbox of your replication agent on Author

     

    3. One of the publisher faulty to responed with 504 for Timeout error code.

    -> You can login to Publisher and see if the page exist on each publisher

     

     

    K
    kiranparab
    Level 3
    November 3, 2020

    Check this as well if any servlet calls on the page

     

    https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-set-timeout-for-sling-servlet-in-aem6-4/qaq-p/311592

     

    https://stackoverflow.com/questions/26742580/504-gateway-time-out-the-server-didnt-respond-in-time-how-to-fix-it

     

      S
      SebNamekAuthor
      Level 2
      November 3, 2020
      I don't think these help. The resource is just a simple http page, which should also be cached
      Terms & ConditionsAccessibility statement

      Loading footer...