Our AEM CMS cloud environments are in Europe. Our backend systems (for
login, may payment, purchase etc) are also in Europe. Unfortunately,
Adobe dont give fixed egress IPs by default, and fixed IPs are required
for our AEM instances to communicate to our various backend APIs (they
have to be whitelisted). We have to request fixed IPs for each env, each
time they are rebuilt. The fixed IP they give us is a single USA IP. The
non fixed IPs are from Europe, but they change every day. We noticed
We frequently need to log something (e.g. audit or unusual events, or
just something we want to keep track of) on the production instance.
However, the only log level available on prod is log.error. So we use
log.error for general logging on production. This has the unfortunate
side effect that we cant search for errors in the prod logs, as there
are a lot of non errors in there. Any better suggestions?
Adobe admitted that they updated production to oracle java 11.0.14 which
has a well documented and already fixed P1 bug. This took down our sites
for around 10 hours as we did not know where the problem came from. We
hotfixed our prod env by downgrading http requests to http 1.1. We could
not reproduce in our dev cloud envs as adobe updated prod before they
updated dev. They updated dev 2 days later to the same broken version of
java. In our industry, 10 hours of down time can cost anything from...
JDK 11.0.14 has a well known major P1 bug where it incorrectly inserts
both host and authority header with http 2.0 requests, causing http 400
malformed exception responses when hitting nginx and other API providers
(notably google) This is the bug in
has been patched some time ago in 18.104.22.168 On monday 28th March 2022 at
12:30, adobe changed the java version to the unpatched 11...
What we are seeing from AEM cloud is its incorrectly setting both host
and authority headers, which is a major bug only present in open JDK
11.0.14. Because it sets both headers, when our servlets try to call an
api with nginx in front of it, nginx responds with 400 due to malformed
request. This has caused us significant downtime. Adobe should be ...
Hi, thanks for the reply, but we need to know exactly which version 11
is being used. e.g. oracle or openjdk. 11.0.10 or 11.0.14 etc. This is
because our site went down for some time, and the only explanation is
that Adobe are using 11.0.14 openJDK, which has a known bug. However,
Adobe should be using Oracle JAva, which is more reliable.
Since launching our sites a year ago, we have suffered constant issues
with calling APIs and 3rd parties from servlets. This includes GOAWAY
being randomly received, to invalid headers being appended and different
Envs having different java http request characteristics with the same
code. Is there any way to find out what version of Java is running on a
particular env? There doesn't seem to be anything in cloud manager or
dev console. We have seen for example that openjdk 11.0.14 has some