Troubleshooting Adobe Experience Manager troubleshooting-aem
The following section covers some issues that you may encounter when using AEM (Adobe Experience Manager), together with suggestions on how to troubleshoot them.
Troubleshooting scenarios for Administrators troubleshooting-scenarios-for-administrators
The following table provides an overview of problems that administrators can troubleshoot:
Installation Issues installation-issues
See Common Installation Issues for information about the following troubleshooting scenarios:
- Double-clicking the Quickstart jar has no effect or the JAR file with another program (such as archive manager).
- Applications running on CRX throw out-of-memory errors.
- The AEM Welcome screen does not display in the browser after double-clicking AEM Quickstart.
Methods for Troubleshooting Analysis methods-for-troubleshooting-analysis
Making a Thread Dump making-a-thread-dump
The thread dump is a list of all the Java™ threads that are currently active. If AEM does not respond properly, the thread dump can help you identify deadlocks or other problems.
Using Sling Thread Dumper using-sling-thread-dumper
- Open the AEM Web Console; for example, at
https://localhost:4502/system/console/
. - Select the Threads under Status tab.
Using jstack (command line) using-jstack-command-line
-
Find the PID (process id) of the AEM Java™ instance.
For example, you can use
ps -ef
orjps
. -
Run:
jstack <pid>
-
Shows the thread dump.
>>
output redirection:jstack <pid> >> /path/to/logfile.log
See the How to take Thread Dumps from a JVM documentation for more information
Checking for unclosed JCR sessions checking-for-unclosed-jcr-sessions
When functionality is developed for AEM WCM, JCR Sessions may be opened (comparable to opening a database connection). If the opened sessions are never closed, your system may experience following symptoms:
- The system becomes slower.
- You can see much of CacheManager: resizeAll entries in the log file; the following number (size=<x>) shows the number of caches, each session opens several caches.
- From time to time the system runs out of memory (after a few hours, days, or weeks - depending on the severity).
To analyze unclosed sessions and find out which code is not closing a session, see the Knowledge Base article Analyze Unclosed Sessions.
Using the Adobe Experience Manager Web Console using-the-adobe-experience-manager-web-console
The status of the OSGi bundles can also give an early indication of possible issues.
-
Open the AEM Web Console; for example, at
https://localhost:4502/system/console/
. -
Select Bundles under OSGI tab.
-
Check:
- the Status of the bundles. If any are Inactive or Unsatisfied, try to stop and restart the bundle. If the issue persists, investigate further using other methods.
- whether any of the bundles have missing dependencies. Such details can be seen by clicking the individual bundle Name, which is a link (the following example does not have any issues):