I'm currently facing the issue on AEM 6.3 version. We are provisioning AEM using AWS and Terraform. As soon as the ec2 spins up (Author instance/pub instance ), I get a problem that the java application doesn't start.
I normally do as work around:
./crx-quickstart/bin > ./status > to check the status > not connected ../crx-quickstart/bin > ./stop and ./start and check the ./status again.
i tried one method as well
./crx-quickstart/conf > sudo rm controlport
./crx-quickstart > ./stop and ./start again ....... Even this method couldn't solve the problem.
Is there a feasible solution for this kind of problem.
how to check heap space:
ps -ef | grep java | grep Xmx ( example of publisher, same for author as well)
At first, you would need to identify what is causing the heap space to grow What background threads or processes are consuming on your VM using Java or your AEM instance. There could be numerous reasons of Java heap space issue such as intensive resource consumption, unclosed resources in code base causing memory leaks, etc.