Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM Is Not Responsive

ForrestLi
Level 2
Level 2

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

ForrestLi_0-1639973031098.png

 

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

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

ForrestLi_1-1639973095524.png

 

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

1 Accepted Solution
BattiniSravan
Correct answer by
Level 4
Level 4

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

View solution in original post

8 Replies
manikanthar1295
Level 5
Level 5

Hi,

 

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

 

Regards

Manikantha R

milind_bachani
Level 5
Level 5

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

ForrestLi
Level 2
Level 2

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

BattiniSravan
Level 4
Level 4

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.

BattiniSravan
Correct answer by
Level 4
Level 4

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

View solution in original post

Sudharsan_Selv1
Level 2
Level 2

 

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-ho...

 

Thanks

Sudharsan