- Administering User Guide overview
- Sites Features
- Website Administration
- Asynchronous Jobs
- Reusing Content: Multi Site Manager and Live Copy
- Live Copy Overview Console
- Configuring Live Copy Synchronization
- Creating and Synchronizing Live Copies
- MSM Rollout Conflicts
- Troubleshooting MSM Issues and FAQ
- MSM Best Practices
- Translating Content for Multilingual Sites
- Managing Translation Projects
- Identifying Content to Translate
- Preparing Content for Translation
- Creating a Language Root Using the Classic UI
- Connecting to Microsoft Translator
- Configuring the Translation Integration Framework
- Language Copy Wizard
- Translation Enhancements
- Translation Best Practices
- Configurations and the Configuration Browser
- AEM FAQs
- Operations
- Dashboards
- Operations Dashboard
- Backup and Restore
- Data Store Garbage Collection
- Monitoring Server Resources Using the JMX Console
- Working with Logs
- Audit Log Maintenance in AEM 6
- Configure the Rich Text Editor
- Configuring RTE for Producing Accessible Sites
- Configuring Undo for Page Editing
- Configure the Rich Text Editor plug-ins
- Configure the Video component
- The Bulk Editor
- Configuring Email Notification
- The Link Checker
- Troubleshooting AEM
- Managing Access to Workflows
- Starting Workflows
- Administering Workflows
- Administering Workflow Instances
- Using cURL with AEM
- Proxy Server Tool (proxy.jar)
- Configuring for AEM Apps
- Configuring Search Forms
- Tools Consoles
- Reporting
- Configuring Layout Container and Layout Mode
- Editor
- Enabling Access to Classic UI
- Admin Consoles
- Security
- User Administration and Security
- User, Group and Access Rights Administration
- Security Checklist
- OWASP Top 10
- Running AEM in Production Ready Mode
- Identity Management
- Adobe IMS Authentication and Admin Console Support for AEM Managed Services
- Creating a Closed User Group
- Mitigating serialization issues in AEM
- User Synchronization
- Encapsulated Token Support
- Single Sign On
- How to Audit User Management Operations in AEM
- SSL By Default
- SAML 2.0 Authentication Handler
- Closed User Groups in AEM
- Granite Operations - User and Group Administration
- Enabling CRXDE Lite in AEM
- Configuring LDAP with AEM 6
- Configure the Admin Password on Installation
- Service Users in AEM
- Encryption Support for Configuration Properties
- Handling GDPR Requests for the AEM Foundation
- Principal View for Permissions Management
- Content Disposition Filter
- Custom User Group Mapping in AEM 6.5
- Same Site Cookie Support
- Personalization
- Integration
- Integrating with Third-Party Services
- Integrating with Salesforce
- Integrating with Adobe Target
- Integrating with Adobe Learning Manager
- Integrating with Adobe Analytics
- Connecting to Adobe Analytics and Creating Frameworks
- Configuring Link Tracking for Adobe Analytics
- Mapping Component Data with Adobe Analytics Properties
- Configuring Video Tracking for Adobe Analytics
- Integration with Adobe Analytics using IMS
- HTTP2 Delivery of Content FAQ
- Troubleshooting your Adobe Campaign Integration
- SharePoint Connector Licenses, Copyright Notices, and Disclaimers
- SharePoint Connector
- DHTML Viewer End-of-Life FAQs
- Integrating with Adobe Campaign Classic
- Related Community Articles
- Integrating with Adobe Campaign Standard
- Flash Viewers End-of-Life Notice
- Integrating with Adobe Dynamic Tag Management
- Opting Into Adobe Analytics and Adobe Target
- AEM Portals and Portlets
- Integrating with Dynamic Media Classic (Scene7)
- AEM Livefyre Recipes
- Troubleshooting Integration Issues
- Integrating with BrightEdge Content Optimizer
- Catalog Producer
- Integrating with Silverpop Engage
- Integrating with Adobe Campaign
- Integrating with ExactTarget
- Analytics with External Providers
- Integrating with the Adobe Marketing Cloud
- Manually Configuring the Integration with Adobe Target
- Prerequisites for Integrating with Adobe Target
- Integration with Adobe Target using IMS
- Adobe Classifications
- Solutions Integration
- Exporting Experience Fragments to Adobe Target
- Best Practices for Email Templates
- Integrating with Livefyre
- Best Practices
- Content Management
Troubleshooting Adobe Experience Manager
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).
Troubleshooting scenarios for Administrators
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 |
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
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
- Open the AEM Web Console; for example, at
https://localhost:4502/system/console/. - Select the Threads under Status tab.
Using jstack (command line)
-
Find the PID (process id) of the AEM Java™ instance.
For example, you can use
ps -eforjps. -
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
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
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):
Resources
Adobe Account
