Adobe Experience Manager AD0-E124 Release Date

Unclosed JCR sessions are a classic cause of memory leaks in AEM applications. When custom backend code opens a JCR Session or ResourceResolver but fails to close it within a finally block, the garbage collector cannot reclaim that memory. Over time, these open sessions accumulate in the heap memory, causing the system to slow down and eventually leading to unpredictable OutOfMemory (OOM) crashes. Restarting the instance clears the heap, temporarily mitigating the issue until the unclosed sessions build up again. This issue is agnostic of visitor peaks or runmodes (author/publish).

To manually migrate a package between two AEM instances via the command line, the process involves two distinct curl commands using the Jackrabbit Package Manager API.

Download: You must download the generated .zip file from the source (STG) environment using -O to save the remote file locally.

Upload & Install: You must upload the local file to the target (PROD) environment and simultaneously install it by passing the -F file=@ < filename > along with the multipart form parameters -F install=true and -F force=true to the /crx/packmgr/service.jsp endpoint.

In the AEM Dispatcher farm configuration, high-frequency replication events can cause "cache stampedes" where the cache is constantly invalidated, forcing all traffic back to the publish instances simultaneously and spiking CPU. The /graceperiod property mitigates this. When set, it defines a window of time (e.g., 2 seconds) during which the Dispatcher will continue to serve "stale" (recently invalidated) cached content to end-users while a single request is sent to the publish tier to fetch the new content. Once fetched, the cache is updated. This effectively throttles invalidation spikes and protects the publish instances from traffic overloads.