Some JMX beans in AEM don't properly close their JCR session, which causes the errors you see.I opened some Daycare issues to report that.Best is to whitelist only the JMX beans you want to extract data from (depends on your monitoring needs).Download the prometheus Java agent jar as described on G...

Yes I do. Quite easy actually. Just use the java agent and put the required java startup parameters in your CQ_JVM_OPTS environment variable before starting AEM. Be be sure to whitelist only the beans you need. By default all JMX beans are monitored and in AEM that is quite a lot.

In the past I was indeed thinking the same, but the overhead of doing whitespace compression is much bigger than the gain of just enabling gzip compression on the non-minified content. Gzip is pretty good in compressing spaces as well.More at https://www.peterbe.com/plog/html-whitespace-compression ...

Better to use gzip compression on the dispatcher. More efficient than this.

But I do think that the sentence "A static resource can only be accessed via the proxy, if it resides below a resource below the client library folder." should be rephrased as "A static resource can only be accessed via the proxy, if it resides below a 'resources' directory below the client library ...

No I don't prajwalreddy​. I was trying to get Adobe staff to tell us something useful. But it appears smacdonald2008​ also dodged the question . But if I read https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/clientlibs.html#LocatingaClientLibraryFolderandUsingtheProxyClientLibra...

I guess the real question is where to put assets like your web fonts in AEM 6.4 and above. /apps has always been blocked by the dispatcher and /etc/clientlibs was not. That is why this construction used to work. But as /etc becomes a no-go zone, and you have to put your website design in /apps, thes...

This is ok. Camelcase is converted into kebab-case by jquery. See https://api.jquery.com/data/#data-html5. Does the HTML reflect that?

As I see it, you have 4 vanity urls enabled:/geogov/testvanity/geohome/testingYou should be able to request them through the dispatcher. The file /tmp/vanity_urls should have the same content. If not, it’s probably bad configurati of the dispatcher or a file permission problem. Also so note that due...

Try to run this on your dispatcher manually:curl -v http://<insert hostname of your publisher here>:4502/libs/granite/dispatcher/content/vanityUrls.htmlDoes it work? Or do you have an error?And did you publish your content page after you entered the vanity URL property?