@Jörg_Hoh thank youI just reviewed the threaddump once again, and we only got 29 RUNNABLE (running).Hmm, why did our AEM publish keep crashing?

While running a UnitTest debugger, I am getting this errorError:osgi: [site.core] Classes found in the wrong directory: {META-INF/versions/9/javax/xml/bind/ModuleUtil.class=javax.xml.bind.ModuleUtil}How do I solve this? There is nothing on Google that can help me.

We have production, staging, qa, and dev cloud environments. We want to re-sync all the content from production to staging, qa, and dev. What is the best way for us to do this in an automated way?

@Jörg_Hoh , do you think you can help me?

One of our publish servers keeps getting CPU usage notifications for 90% consumption. We pulled down the thread dumps, and analyzed it on the IBM Thread dump analyzer. We realized that there are many instances of jdk.internal.misc.Unsafe.park, around 303 threads (look below for the total amount of I...

Thank you for the response, but/content/my-brand/static/*   should also be accessible to our public users too. Would you do some apache rewriting to [PT] the request to the files? what happens when an author accidentally publishes this file? Also we don't want the authors to see these.Wouldn't /etc/...

In our AEM we have a service call that takes a long while, around 2 minutes to have a response. Once we get the response, we will be building nodes in AEM as a caching mechanism. My question is, will the slow 2 minutes to have a response impact my AEM authors performance? Will my authors suffer from...

Thank you, we have done this, but the question is. When we deploy a new bundle, does these threads get closed?

My organization has a few JSON files that we like to re-use across out website. countries.jsoncountries_city.jsoncountries_zip.jsonThey will be used for the forms drop down, and some sort of backend logic.Where is the best place to store these files.We were thinking of /etc/designs/my-brand/static/*...

Our AEM website has many error/warning signaling us that a resolver has not been closed, when it is opened.When we deploy a new version Bundle, will all these messages goes away? or would we be forced to restart AEM? How can we close all the resolvers, and continue with AEM's website without restart...