Expand my Community achievements bar.

SOLVED

HOw resolve error while starting AEM in Debug mode?

Avatar

Level 3

Facing error while starting AEM in Debug mode.

Anilkumar9_0-1709287306916.png

Below is the command used to run AEM in debug mode

java -Xmx2048M -agentlib:jdwp=transport=dt_socket,address=8888,server=y,suspend=n -jar aem-author-p4502.jar

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Open command prompt and go to same folder where jar file is present as shown below and run below inline command

Imran__Khan_1-1709288401965.png

java -jar cq65-author-p4502.jar -fork -forkargs -- -Xdebug -Xrunjdwp:transport=dt_socket,address=30303,suspend=n,server=y -Xmx1500m -XX:MaxPermSize=300m
Please check the highlighted port name.

Note: Restart system it will work as your instance didn't get shutdown or wait for sometime.

View solution in original post

3 Replies

Avatar

Level 8

Hi @Anilkumar9 

 

Not sure, why are facing the issue, even though you are using the proper command. I have tried this way.  Added these in the start.bat file.

Then. opened the command prompt in bin folder > start.bat

if not defined CQ_JVM_OPTS set CQ_JVM_OPTS=-Xmx2048m -XX:MaxPermSize=512M -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n
::* add the required JPMS modules, if needed
java --add-modules java.se.ee --version > nul 2>&1
if %errorlevel% EQU 0 set CQ_JVM_OPTS=--add-modules java.se.ee %CQ_JVM_OPTS%

Avatar

Correct answer by
Community Advisor

Open command prompt and go to same folder where jar file is present as shown below and run below inline command

Imran__Khan_1-1709288401965.png

java -jar cq65-author-p4502.jar -fork -forkargs -- -Xdebug -Xrunjdwp:transport=dt_socket,address=30303,suspend=n,server=y -Xmx1500m -XX:MaxPermSize=300m
Please check the highlighted port name.

Note: Restart system it will work as your instance didn't get shutdown or wait for sometime.

Avatar

Community Advisor

@Anilkumar9 

Can you check if you are already running an AEM instance on port 4502 or if any other process is using port 4502

If yes, try to kill the process and then try