Expand my Community achievements bar.

SOLVED

Issue Setting Up AEM SDK Local Environment for Practice

Avatar

Level 2

Hello Adobe Community,

 

I’m currently trying to set up my local environment using the AEM SDK version aem-sdk-2023.12 for practice purposes.

RohitKu17_0-1727447449273.png

 

However, I'm encountering some issues:

  1. First-time startup worked fine, but now when I try to start the instance a second time, it fails to launch.
  2. I'm looking for best practices or steps to correctly set up a local AEM environment for development and testing, including any configuration tweaks or troubleshooting advice.
  3. Any additional resources or recommendations for working with the SDK in a local environment would be greatly appreciated.
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @RohitKu17 

Can you check the java version?

try to allow warnings with below flag when you start aem using jar

 --illegal-access=permit

 



Arun Patidar

View solution in original post

16 Replies

Avatar

Level 9

Hi @RohitKu17,

the most important thing is to ensure that you always gracefully shut down your AEM instance like explained here: https://aemgeeks.wordpress.com/2017/08/24/starting-and-stopping-aem-instance/

Then you should be able to start it again with no issues.

 

Hope it helps,

Daniel

Avatar

Community Advisor

Hi,

 

In addition to what @daniel-strmecki mentioned, please run the latest version of the AEM SDK. You could likely encounter issues with older versions, especially if you are installing custom code. Also, could you elaborate on the errors you are seeing when you try to run AEM the second time?



Esteban Bustamante

Avatar

Level 2

@EstebanBustamante

Please let me know which one is the latest version used by You and others 

 

RohitKu17_0-1727531121083.png

It start and then exits automatically 

Avatar

Community Advisor

@RohitKu17 so what do you see in the logs? error.log and stdout.log? You can find the latest version of AEM here: https://experience.adobe.com/#/downloads/content/software-distribution/en/aemcloud.html . Can you add the -v into your start command, this will input more info in the console.



Esteban Bustamante

Avatar

Community Advisor

Hi @RohitKu17,

The best resource to setup AEM Local SDK is Set up local AEM SDK
Can you share the error logs when you try to fire up the instance the second time - Does deleting the crx-quickstart folder and running the java-jar arm-author-p4502.jar work for you?

Please note You cannot start the AEM as Cloud Service Quickstart Jar by double-clicking.

 

Hope this helps!
Rohan Garg

Avatar

Level 2

@Rohan_Garg 

Yes, it is working. But do I have to delete that folder every time before I start the instance a second time?

Thanks for answering 

Avatar

Community Advisor

Hi @RohitKu17 ,

We don't need to delete crx-quickstart every time unless instance get corrupt.

 If its started well and working fine.

One approach can be just double click on start.bat file (for windows) or run ./start(linux) and stop.bat file or ./stop command to stop from next time

These files are present in /crx-quickstart/bin folder

MukeshYadav__0-1727531885414.png

We can even edit start file to setup/change parameters like port number or run modes.

Thanks,

Avatar

Correct answer by
Community Advisor

Hi @RohitKu17 

Can you check the java version?

try to allow warnings with below flag when you start aem using jar

 --illegal-access=permit

 



Arun Patidar

Avatar

Level 2

Hi @arunpatidar 

Java version 11.0.23

 

404 when i try to run it second time 

RohitKu17_0-1727770237972.png

 

Avatar

Level 2

Hi @arunpatidar 

 

So if i used flag

 --illegal-access=permit

It is working fine every time.

Thanks

Avatar

Community Advisor

Can you post the error.log when you fire up the instance the second time?