Adobe Professional Services consultant Feike Visser has posted four excellent articles on Adobe’s new (in AEM 6) markup language Sightly. It was designed so that designers of web pages don’t have to mess with Java code in JSPs.
What a well-tuned CQ 5.6.1/JDK 1.7.0_51 “author” JVM looks like in Java 8’s JVisualVM tool (with the “Visual GC” plugin), when it is under heavy load (web pages being created/published, JPG image assets being ingested, and PDF documents being ingested).
Sometimes, code from components you have no control over as a system administrator starts littering the error.log with useless (to you) INFOrmational messages. This causes logs to bloat, increasing disk I/O, storage costs and additional CPU cycles.
You can use the “Apache Sling Logging Logger Configuration" OSGi configuration at /system/console/configMgr to suppress a message such as follows:
28.02.2014 01:55:05.596 *INFO* [Thread-1078954] com.corporation.generics.services.services.impl.GsaServiceImpl »»» Entering the buildUrl method
1) Raise the “Log Level” threshold one step higher (from INFO to WARN)
2) In the “Logger” field, enter the name of the package causing trouble (com.corporation.generics.services.services.impl.GsaServiceImpl)
It takes effect immediately on saving - no re-start necessary.
The ”Day CQ WCM Page Statistics" OSGi configuration lets you configure the "publish" instances with the IP address of the "author" instance(s) so that page impressions statistics can be recorded in "author" using tracker.js ( /libs/wcm/stats/tracker.js ).
See screenshot below (replace localhost and 4502 with your “author” instance’s DNS name and port):
For example, loading the main Geometrixx Outdoors page on “publish” will trigger a GET request on “author” like this:
If configured properly, when you load up that page in “author” ( /siteadmin#/content/geometrixx-outdoors ), you should see that the number for that page under the “Impressions” column has gone up by 1.
If not configured properly, this will trigger an HTTP response of 403 Forbidden in “publish”.
You can also leave the URL blank to disable this altogether (thanks to my colleague Caleb Pryor for that suggestion).
Tracking page impressions does increase load on your “author” instance. If no one cares about keeping track of page impressions on “publish”, then you are better off disabling it. It is definitely NOT a good indicator of readership because you can get that information only from your CDN. If you don’t use a CDN, the authoritative information on readership will reside on the Apache (Dispatcher) logs.