To fully qualify a ticket so support can quickly process and understand the issue, it's necessary to gather certain information.

Information to provide in the ticket

Check and install the tool package to help on collecting information, you can find it here on tool.

When there's an issue with CQ, it's necessary to provide the following information:

  • Link to the documentation describing the product feature matching your issue
  • Information about the browser version, if related to a browser-specific issue
  • JVM parameters currently applied
  • Collected data using the system information collector tool or manually using following method

Collect system information (manual method)

  1. Version of CQ or CRX, and hot fixes and feature pack applied, following output helps: curl -u admin:admin http://localhost:4502/crx/packmgr/service.jsp?cmd=ls > package_list.xml (adapt it for your login/password and host/port)
  2. Apache Felix Configuration Status, under http://localhost:4502/system/console/config/configuration-status.zip (default installation)
  3. CRX repository.xml and all workspace.xml (crx.default, crx.system for CRX <2.0)
  4. List of files and log files on the file system like describe in the article "Analyze Persistence Problems"

Other possible source of information to collect

In general

When instructions are provided to reproduce the issue, check that it works on an instance that is rebuilt based on the same instructions. If you cannot reproduce it somewhere else, it could be difficult for the support team to reproduce it too. And that could be a hint that the issue needs more content or description. A package or some clear steps with screenshot or screen recording can be useful. Exact timestamp when the problem is observed or a clear time range is also a good practice to add in the description of the issue.

Performance-related issues

If the issue is performance-related, provide thread dumps as described in the article "Analyze Slow and Blocked Processes", at least ten thread dumps with interval of 10 seconds. And, if you can use prof.jsp, use at least a stack depth of 64 with interval of 200 ms. Collect this data for about five minutes.

Memory-related issues

If there is a memory-related issue (out of memory message appear in your logs for example), provide the information as describe in the article "Analyze Memory Problems."

Do this step for all instances in the cluster if applicable.

Send/attach the collected data

Send all in a single archive. If that is too large for the ticket, send it on the sjftp.day.com as documented in the ticket creation form page. Provide the information in the ticket at creation or as soon as possible after creation with the additional information and description that can help analyze the problem.

Change the loglevel to DEBUG according to the related issue

To get better quality in qualifying your ticket, use the Apache Felix Webconsole > Configuration panel. Add a Logger configuration for DEBUG messages for the different part of the code related to your issues.

For example:

com.day.cq.replication.impl for replication issues

org.apache.sling.event.impl for Eventing-related issues

For example, you can find the package or category name for the logger by opening the bundle information in Apache Felix Webconsole > Bundles panel.

Adding such information can help resolve the issue faster.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy