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.
But I am not find a session leak in the JMX page.
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 : 126.96.36.199
Environment : Windows 10
Solved! Go to Solution.
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.
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
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 ). 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).