Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

AEM local server stops immediately after starting.

Avatar

Level 2

 aem-sdk-2023.12.14697.20231215T125030Z-231200 % java -jar aem-author-p4502.jar

Loading quick start properties: default

Loading quickstart properties: instance

Low-memory action set to fork

Using 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork arguments=[-Xmx1024m, -XX:MaxPermSize=256m]

The JVM reports a heap size of 4096 MB, meets our expectation of 1024 MB +/- 20

Setting properties from filename '/Users/btg703324/Downloads/aem-sdk-2023.12.14697.20231215T125030Z-231200/aem-author-p4502.jar'

Option '-quickstart.server.port' set to '4502' from filename aem-author-p4502.jar.

Verbose option not active, closing stdin and redirecting stdout and stderr

Redirecting stdout to /Users/btg703324/Downloads/aem-sdk-2023.12.14697.20231215T125030Z-231200/crx-quickstart/logs/stdout.log

Redirecting stderr to /Users/btg703324/Downloads/aem-sdk-2023.12.14697.20231215T125030Z-231200/crx-quickstart/logs/stderr.log

Press CTRL-C to shutdown the Quickstart server...

WARNING: An illegal reflective access operation has occurred

WARNING: Illegal reflective access by org.apache.sling.commons.threads.impl.ThreadLocalCleaner (launchpad:resources/install/15/org.apache.sling.commons.threads-3.2.22.jar) to field java.lang.Thread.threadLocals

WARNING: Please consider reporting this to the maintainers of org.apache.sling.commons.threads.impl.ThreadLocalCleaner

WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations

WARNING: All illegal access operations will be denied in a future release

@Btm-JTGJ077Y4C aem-sdk-2023.12.14697.20231215T125030Z-231200 %

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 7

Hello @UtkarshDa there could be many reasons for this behaviour. I would start by checking the java version. JDK 8 & 11 are supported versions. Also do you get any other errors apart from what you posted above ?

 

Thanks

Narendra

View solution in original post

1 Reply

Avatar

Correct answer by
Level 7

Hello @UtkarshDa there could be many reasons for this behaviour. I would start by checking the java version. JDK 8 & 11 are supported versions. Also do you get any other errors apart from what you posted above ?

 

Thanks

Narendra