The following section covers some issues that you may encounter when using AEM (Adobe Experience Manager), together with suggestions on how to troubleshoot them.
If you are troubleshooting authoring issues in AEM, see Troubleshooting for Authors.
When experiencing problems, it is also worthwhile checking the list of Known Issues for your instance (release and service packs).
The following table provides an overview of problems that administrators can troubleshoot:
Role | Problem |
System Administrator | Double-clicking the Quickstart jar does has no effect or opens the jar file with another program (for example, archive manager) |
System Administrator |
My application running on CRX throws out-of-memory errors |
System Administrator |
The AEM Welcome screen does not display in the browser after double-clicking AEM CM Quickstart |
System Administrator admin user |
Making a Thread Dump |
System Administrator admin user |
Checking for unclosed JCR sessions |
See Common Installation Issues for information about the following troubleshooting scenarios:
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.
https://localhost:4502/system/console/
.Find the PID (process id) of the AEM Java™ instance.
For example, you can use ps -ef
or jps
.
Run:
jstack <pid>
Shows the thread dump.
You can append the thread dumps to a log file by using the >>
output redirection:
jstack <pid> >> /path/to/logfile.log
See the How to take Thread Dumps from a JVM documentation for more information
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:
To analyze unclosed sessions and find out which code is not closing a session, see the Knowledge Base article Analyze Unclosed Sessions.
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: