How to kill the aem instance running in background | Community
Skip to main content
AdobeID24
Level 5
September 23, 2019

How to kill the aem instance running in background

  • September 23, 2019
  • 4 replies
  • 11532 views

my instance is running if i access localhost:4502/crx/de/index.jsp ....but not jar file is open not start.bat file is ruuning over cmd ...i cant see any thing opened in my machine .

It means my instance is running in background .

How I can stop my aem instance to run in windows ?

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

4 replies

ArpitVarshney
Community Advisor
Community Advisor
September 23, 2019

Hi,

It seems like AEM didn't stop properly.

Please open your command prompt and run below commmands

netstat -ano | findstr :4502

It will return you PID(note that down)

After that run the below command:

taskkill /PID <typeyourPIDhere> /F

Please refer this blog Windows Kill Process By PORT Number.

sunjot16
Adobe Employee
Adobe Employee
September 23, 2019

You can find the instance running in background/apps, by going to Task Manager (Ctrl + Shift + Esc) and there, if you find the AEM instance running in Apps as Java(TM) Platform SE binary, you can click on "End Task" after right-clicking on it.

Adobe Employee
September 23, 2019

you can find AEM process PID by using:

ps -ef | grep java | grep cq-quickstart

Adobe Employee
September 23, 2019

You might want to check services if AEM is started as a windows service. Check [1] for more details.

[1] https://aemexperts.blogspot.com/2019/03/installing-and-starting-adobe.html

Adobe Employee
September 24, 2019

ProTip : If you need to manually kill the java process . ENSURE that AEM is not writing to disk or you risk data corruption.

So a quick way to do this is to check the segmentstore /crx-quickstart/repository/segmentstore and view the last modified timestamps on all the TAR files. Ensure that it hasn't written to disk in the last few minutes before you kill the process. Otherwise when you bring it back up you could have issues trying to mount the repository.

Cheers.