Hi, We are getting 504 Gateway Timeout server error when trying to
access AEM author instance in our stage author environment. In error
logs we see following "Failed to create checkpoint warning messages when
this happens: 14.10.2020 04:01:01.940 *WARN*
org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler Failed to
create checkpoint 8a02222a-3c8d-44dc-8066-05e78ea31fad in 10
seconds.14.10.2020 04:01:01.940 *W...
@SundeepKatepallyAnother interesting thing to note is, on a fresh
instance it takes only 5-7 minutes to complete the deployment. If it's a
consistent product issue, it should happen even on a fresh instance as
well. I doubt if there are more conditions involved when this is
supposed to occur. May be when you have lot of content/asserts available
in the repository.
Thanks @SundeepKatepally for your valuable inputs. It helps. We also
have a ticket raised with AMS to help us investigate the issue and its
been few weeks now, but they have not informed about this product issue
yet. It is now a business critical issue for us, as we are not sure what
are other impacted areas, if any. It seems like we have to live with it
until they provide us a fix for the same.
Thanks @SundeepKatepally for your response. Did you also encounter that
sometimes it results in server becoming unresponsive? I have worked with
6.4.2 version in two other projects but have not faced this issue there.
Does it happen in any specific scenario? Moreover our author takes
around 10-15 minutes to come back but publisher usually take 30-40
Hi, We are facing following two unusual environment issues in our AMS
managed stage environments:With deployment either of author or publisher
instances becomes unresponsive and service restart is the only option to
bring them back-upDeployment takes longer time 30-40 minutesAfter
Analyzing logs we found that AEM restarts many of its services and
sometimes these restart of services is multiple times. This is one of
the reason for long deployment duration we are facing. Our deployment