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
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM start.bat startup error "Could not find or load main class Website\author\crx-quickstart\bin\"

irmantasl423171
Level 1
Level 1

Trying to run start.bat to set up debugger in Eclipse, but get the Error:Could not find or load main class Website\author\crx-quickstart\bin\ when I try to run in. Any ideas?

 

irmantasl423171_0-1598831168943.png

 

debugger debugging eclipse
1 Accepted Solution
Varun_Shakya
Correct answer by
Community Advisor
Community Advisor

here is one similar thread

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/could-not-find-the-main-cl...

double check these points as well

 

Step 1: Add the Remote Debugging JVM Parameter

  1. To use remote debugging, you must start AEM with this JVM parameter:
    -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n

You can add the parameter by doing any of the following:

  • Add it to your crx-quickstart/bin/start script CQ_JVM_OPTS environment variable (so your server always starts in debug mode).
  • Include it as a parameter when starting AEM with java -jar directly. For example, java -Xmx512m -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -jar cq-author-4502.jar

Notes

  • If necessary, you can change the port defined under "...,address=8000,..." from 8000 to something that works better in your environment.
  • If you notice that it isn't working, avoid forking the java process by specifying the -nofork command line option.
  • The start script is located under crx-quickstart/bin

 

Ref:-https://helpx.adobe.com/in/experience-manager/kb/CQ5HowToSetupRemoteDebuggingWithEclipse.html

 

View solution in original post

4 Replies
Varun_Shakya
Correct answer by
Community Advisor
Community Advisor

here is one similar thread

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/could-not-find-the-main-cl...

double check these points as well

 

Step 1: Add the Remote Debugging JVM Parameter

  1. To use remote debugging, you must start AEM with this JVM parameter:
    -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n

You can add the parameter by doing any of the following:

  • Add it to your crx-quickstart/bin/start script CQ_JVM_OPTS environment variable (so your server always starts in debug mode).
  • Include it as a parameter when starting AEM with java -jar directly. For example, java -Xmx512m -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -jar cq-author-4502.jar

Notes

  • If necessary, you can change the port defined under "...,address=8000,..." from 8000 to something that works better in your environment.
  • If you notice that it isn't working, avoid forking the java process by specifying the -nofork command line option.
  • The start script is located under crx-quickstart/bin

 

Ref:-https://helpx.adobe.com/in/experience-manager/kb/CQ5HowToSetupRemoteDebuggingWithEclipse.html

 

View solution in original post

irmantasl423171
Level 1
Level 1

Hi, I've done the steps above already, this is when I ran into the error. This is what got it resolved for me https://stackoverflow.com/questions/39710510/aem6-starting-from-console-with-debug-nofork-options. Executed the following from the command line "java.exe -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=9669,suspend=n -XX:+PrintGC -XX:+UseG1GC -XX:MaxGCPauseMillis=200 -jar aem-quickstart-6.2.1.jar" and it worked. Thank you.

irmantasl423171
Level 1
Level 1

Hi, I've done the steps above already, this is when I ran into the error. This is what got it resolved for me https://stackoverflow.com/questions/39710510/aem6-starting-from-console-with-debug-nofork-options. Executed the following from the command line "java.exe -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=9669,suspend=n -XX:+PrintGC -XX:+UseG1GC -XX:MaxGCPauseMillis=200 -jar aem-quickstart-6.2.1.jar" and it worked. Thank you.