January 18, 2021
Estimated Post Reading Time ~

AEM 6.5 Upgrade to 6.5.7 CFP Causing Unresponsive Instances

Question: 
AEM 6.5 Upgrade to 6.5.7 CFP Causing Unresponsive Instances
We've recently upgraded AEM from 6.5.1 to 6.5.7.

Since we've upgraded from SP 6.5.1 to 6.5.7 we've noticed really poor performance, author and 
publish instance needing restarts nearly every 2-3 days because of becoming unresponsive. No heap dumps or OutOfMemory exceptions.

Logs:
17.01.2021 09:20:02.286 *INFO* [10.142.72.17 [1610900402282] GET /mnt/overlay/granite/ui/content/shell/header/actions/pulse.data.json HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /mnt/overlay/granite/ui/content/shell/header/actions/pulse.data.json not found

Solution:

Checking the thread dumps and further researching internally, It seems you are running into a known issue(CQ-4312194) with SP7 where numerous threads get blocked due to a Timer with the Component Registry (org.apache.felix.scr.impl.ComponentRegistry). This causes the instance to become unresponsive.

  • Follow the steps below to resolve the issue:
    - Install the attached hotfix package (Hotfix-CQ-4312194-FELIX-6252-1.0.zip)
    - This will trigger a restart of a couple of bundles. So, need to wait 3-5 mins
    - Go to <host>:<port>/system/console and make sure the "org.apache.felix.scr" version is updated to 2.1.20


By aem4beginner

2 comments:

  1. Where did you get the download for the hotfix?

    ReplyDelete
  2. This guys all content is copied from others blog and forums. The original post is https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-5-upgrade-to-6-5-7-cfp-causing-unresponsive-instances/qaq-p/391384

    ReplyDelete

If you have any doubts or questions, please let us know.