Adobe Daycare has made available a tool called “Support Info Collector" that collects all relevant data about a particular CQ instance to be able to debug a problem, including config files and multiple (10), consecutive thread dumps.
Collecting common info Copying D:\CQ\author\crx-quickstart\repository\repository\nodetypes\custom_nodetypes.xml to c:\TEMP\Test.\tmp1403273878115\xml_files Copying D:\CQ\author\crx-quickstart\repository\repository\privileges\custom_privileges.xml to c:\TEMP\Test.\tmp1403273878115\xml_files Copying D:\CQ\author\crx-quickstart\repository\repository.xml to c:\TEMP\Test.\tmp1403273878115\xml_files Copying D:\CQ\author\crx-quickstart\repository\workspaces\crx.default\workspace.xml to c:\TEMP\Test.\tmp1403273878115\xml_files CQ process id found = 9280
Taking thread dump 1/10 … for process 9280 Taking thread dump 2/10 … for process 9280 Taking thread dump 3/10 … for process 9280 Taking thread dump 4/10 … for process 9280 Taking thread dump 5/10 … for process 9280 Taking thread dump 6/10 … for process 9280 Taking thread dump 7/10 … for process 9280 Taking thread dump 8/10 … for process 9280 Taking thread dump 9/10 … for process 9280 Taking thread dump 10/10 … for process 9280 Collecting online info SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Compressing collected file into a single archive file Removing temporary files Collected information completed, attach it to your ticket or send it to our ftp
NOTE: DocumentNodeStoreService.cfg is for MongoMK, SegmentNodeStoreService.cfg is for TarMK
2) Delete the .zip file /crx-quickstart/cq-6.0-featurepack-4137-1.0.zip
3) Depending on the MK you are using, delete the .cfg file you don’t need. For example, if you’re using TarMK, delete /crx-quickstart/install/org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.cfg
4) Edit org.apache.jackrabbit.oak.plugins.blob.datastore.S3DataStore.cfg so that it looks something like this.
See this for information on different S3 endpoints.
Also edit /crx-quickstart/bin/start to look something like this.
AEM 6 performance comparison across various platform options. The index is the time taken (in seconds) to finish workflow processing when two threads simultaneously (remotely) ingest 100 (1 MB) JPGs and 2,000 (1 MB) PDFs.
The Windows machine was a Dell Precision T7500 workstation.
The AWS instance type was m3.xlarge.
The MongoMK test used a three-mongod (2.6.1) replicaset, all instances within the same Amazon AWS “Region”, but in separate “Availability Zones”. 1.7.0_60 JDK.
If you make changes to the Eclipse Jetty servlet engine configuration in /system/console/configMgr (“Apache Felix Jetty Based Http Service”), and end up making a mistake, it is possible that AEM will become inaccessible across the entire cluster. At this point, you’ll need to edit the changes you made on each cluster member one-by-one, and re-start AEM on each.
A common mistake is to edit one of the settings in the OSGi console, and forgetting to make sure that the “HTTP Port” is set to 4502 (it defaults to 8080).
The file to edit is at /crx-quickstart/launchpad/config/org/apache/felix/http.config
If you don’t see this file at that location, note that it’ll only show up once you edit the config at least once.