- Adobe Campaign: Queries against tsEvent take a long time
- How to reset the truststore in AEM
- Audience creation options
- How to look up Launch Darkly flags?
- Adobe Campaign Standard: File Fails to upload if email entries contain “double”
- How to reset the admin password in AEM 6.3
- The Non-Apple SSO TV Provider Authentication Flow
- How to confirm if an MVPD is enabled for Apple SSO
- Change the minification engine for client libraries in AEM
- Adobe Campaign Standard: Can a collection within a collection be used within a JSON payload
- Error: Unable to parse expression ‘@registrationToken’
- How to optimize Oak Lucene indexes to reduce indexing time
- Marketing Channel Instances on Custom Links
- Sprint 7 Exp League Article - 1
- Test - Cont - 2
- How to delete the dispatcher cache without logging into to the Dispatcher server | AEM 6.x
- Test - Coach - EXL - 1
- How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4
- ACC: Workflow best practices - Configuration and monitoring
- How to enable secure cookies in AEM
- Audience Manager to Campaign
- Adobe Campaign Standard: Imported File Transfer activities cannot change external account
- Check and analyze if JCR session leaks in your AEM instance
- Whitelisting the Domain for Requester IDs in Adobe PASS
- Permission denied error from java.io.File.createTempFile
- Discover and Build Audiences
- How can I confirm if SSO is enabled or disabled for my Channel?
- Testing - Cont - EXL -1
- Publishing of references broken on Touch UI
- DRM Error 3324 MachineTokenInvalid Sub Error Code = 111
- How to capture SSAI and Original Manifests Simultaneously
- Adobe Primetime Authentication - Most frequently used terms
How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4
Description
How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4
Environment
AEM 6.4
Resolution
Sometime the JSP classes will not get compiled automatically in Adobe Experience Manager(AEM). Strange UI issues can occur and compilation errors may be seen in the logs. In AEM6.4 libraries are no longer under /var/clientlibs folder, they are in the file system.
- Recompile via AEM Web Console:
-
For classes and Slightly access [1] and click Recompile all JSPs.
-
For clientlibs access [2], click Invalidate Caches then click Rebuild Libraries.
-
Recompile via the file system
- For classes and Slightly cache:
- Search in the AEM instance home folder with command below:
find launchpad/felix -path “/bundle/data/classes” -type d
- Delete the “classes” folder
Note: Classes and Slightly cache is stored in the Apache Sling Commons FileSystem ClassLoader bundle. You can also check the bundle number in the AEM Web Console and access that folder directly on the file system.
- For clientlibs
- Search in the AEM instance home folder with command below:
find launchpad/felix -path “/bundle/data/outputcache” -type d
- Delete “outputcache” folder
Note: Clientlibs is now stored in the Adobe Granite UI Clientlibs. You can also check the bundle number in the AEM Web Console and access that folder directly on the file system.
[1] http://[host]:[port]/system/console/slingjsp
[2] http://[host]:[port]/libs/granite/ui/content/dumplibs.rebuild.html
DOWNLOAD
Shell script cq-force-recompilation64.sh to automate the recompile process on AEM 6.4 Example arguments: ./cq-force-recompilation64.sh crx-quickstart/ http://localhost:4502 admin:admin