AEM Is Not Responsive | Community
Skip to main content
F
ForrestLi
December 20, 2021
Solved

AEM Is Not Responsive

  • December 20, 2021
  • 4 replies
  • 2393 views

Hi All，

 

Every time I start AEM, AEM will not respond after a while.

 

This is what I am seeing in the monitoring page. It is showing the number of active sessions are growning.

http://localhost:4503/libs/granite/operations/content/monitoring/page.html

 

But I am not find a session leak in the JMX page.

http://localhost:4503/system/console/jmx

 

Does anyone know how or where can I find out what is causing this problem? 

 

When AEM is not responsive, error log is no longer produced. For example, if AEM is not resonsive in the 2021-12-21, you will find there is no error log file for 2021-12-21, other logs are work well, like request.log.2021-12-21.

 

AEM : 6.5.7.0

Environment : Windows 10

 

Thanks,

Forrest

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by B_Sravan

okay, please upgrade your Java version to 11. That should resolve your problem.
Thank you.

4 replies

manikanthar1295
manikanthar1295
December 20, 2021

Hi,

 

Can you check logs to find out the root cause of the issue.

 

Regards

Manikantha R

    F
    ForrestLiAuthor
    December 20, 2021

    There is no error in the log.

      milind_bachani
      Adobe Employee
      milind_bachaniAdobe Employee
      Adobe Employee
      December 20, 2021

      Hi @forrestli , what are the params you are using to start the instance ?

      Try using -Xmx1024m -XX:MaxPermSize=256m while starting the instance.
      Probably you should see something in the error.org whenever the instance malfunctions.

      Thanks

        F
        ForrestLiAuthor
        December 20, 2021

        This is my params.

         

        java -Dcrx.debug.sessions=true -Dsun.arch.data.model=32 -XX:MaxPermSize=2048m -Xmx4096M -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8766,server=y,suspend=n -jar aem65-publish-p4503.jar -r publish localdev

          B_Sravan
          Community Advisor
          B_SravanCommunity Advisor
          Community Advisor
          December 20, 2021

          Hi @forrestli, 

          May I know if this is a recent change after installing a service pack or something?
          Also, try changing the JAVA version (sometime back this helped me).
          Thank you.

            F
            ForrestLiAuthor
            December 22, 2021

            I recent upgrade the AEM from AEM 6.1 to AEM 6.5.

              B_Sravan
              Community Advisor
              B_SravanCommunity AdvisorAccepted solution
              Community Advisor
              December 22, 2021

              okay, please upgrade your Java version to 11. That should resolve your problem.
              Thank you.

                S
                Sudharsan_Selv1
                December 29, 2021

                 

                Hi @forrestli 

                Did you analyzed the threaddump? If you find deadlock in SCR Component Registry (refer below) then it is known issue in AEM 6.5.7 and this was addressed in Service Pack 8 or later (refer link [0]). Try upgrading service SP8 or later and see if that works. 

                 

                Deadlock in the SCR Component Registry when many threads are blocked due to org.apache.felix.scr.impl.ComponentRegistry timer. As a result, Experience Manager stops responding for an indefinite time (GRANITE-33125,FELIX-6252).

                 

                [0] https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/service-pack/previous-hotfixes-featurepacks.html?lang=en#experience-manager-6580

                 

                Thanks

                Sudharsan

                 

                 

                  F
                  ForrestLiAuthor
                  February 22, 2022

                  Thanks Sudharsan, the issue been fixed after I updated the service package to 6.5.11  

                  Terms & ConditionsAccessibility statement

                  Loading footer...