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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

AEM 6.4 Quickstart Jar file Not Working

bb2j3z2x
Level 2
Level 2
‎25-07-2019 09:06 PDT

Having some trouble getting the quickstart to run.    What version of JDK for java should I be using?    I downloaded version 8.   So Java SE version is 1.8.0_221.

Right now, when I run the quickstart jar file.    I see this screen but it never advances in the progress bar.      I am on Windows 10 - 64bit.

screenshot.png

Logs show.

25.07.2019 11:44:11.185 *INFO* [FelixStartLevel] org.apache.sling.commons.log.logback.internal.Activator LogbackManager initialized at bundle startup

25.07.2019 11:44:11.190 *INFO* [FelixStartLevel] org.apache.sling.commons.logservice Service [org.apache.sling.commons.logservice.internal.LogServiceFactory,18, [org.osgi.service.log.LogService]] ServiceEvent REGISTERED

25.07.2019 11:44:11.191 *INFO* [FelixStartLevel] org.apache.sling.commons.logservice Service [org.apache.sling.commons.logservice.internal.LogReaderServiceFactory,19, [org.osgi.service.log.LogReaderService]] ServiceEvent REGISTERED

25.07.2019 11:44:11.191 *INFO* [FelixStartLevel] org.apache.sling.commons.logservice BundleEvent STARTED

25.07.2019 11:44:11.196 *ERROR* [FelixDispatchQueue] org.apache.sling.installer.core FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve org.apache.sling.installer.core [12](R 12.0): missing requirement [org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation) Unresolved requirements: [[org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation)])

org.osgi.framework.BundleException: Unable to resolve org.apache.sling.installer.core [12](R 12.0): missing requirement [org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation) Unresolved requirements: [[org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation)]

at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149)

at org.apache.felix.framework.Felix.startBundle(Felix.java:2119)

at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)

at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

at java.base/java.lang.Thread.run(Thread.java:835)

25.07.2019 11:44:11.197 *ERROR* [FelixDispatchQueue] org.apache.sling.installer.factory.configuration FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve org.apache.sling.installer.factory.configuration [13](R 13.0): missing requirement [org.apache.sling.installer.factory.configuration [13](R 13.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api.tasks)(version>=1.3.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.sling.installer.core [12](R 12.0): missing requirement [org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation)] Unresolved requirements: [[org.apache.sling.installer.factory.configuration [13](R 13.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api.tasks)(version>=1.3.0)(!(version>=2.0.0)))])

org.osgi.framework.BundleException: Unable to resolve org.apache.sling.installer.factory.configuration [13](R 13.0): missing requirement [org.apache.sling.installer.factory.configuration [13](R 13.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api.tasks)(version>=1.3.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.sling.installer.core [12](R 12.0): missing requirement [org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation)] Unresolved requirements: [[org.apache.sling.installer.factory.configuration [13](R 13.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api.tasks)(version>=1.3.0)(!(version>=2.0.0)))]

at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149)

at org.apache.felix.framework.Felix.startBundle(Felix.java:2119)

at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)

at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

at java.base/java.lang.Thread.run(Thread.java:835)

25.07.2019 11:44:11.198 *ERROR* [FelixDispatchQueue] org.apache.sling.installer.provider.file FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve org.apache.sling.installer.provider.file [14](R 14.0): missing requirement [org.apache.sling.installer.provider.file [14](R 14.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api)(version>=3.1.2)(!(version>=4.0.0))) [caused by: Unable to resolve org.apache.sling.installer.core [12](R 12.0): missing requirement [org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation)] Unresolved requirements: [[org.apache.sling.installer.provider.file [14](R 14.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api)(version>=3.1.2)(!(version>=4.0.0)))])

org.osgi.framework.BundleException: Unable to resolve org.apache.sling.installer.provider.file [14](R 14.0): missing requirement [org.apache.sling.installer.provider.file [14](R 14.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api)(version>=3.1.2)(!(version>=4.0.0))) [caused by: Unable to resolve org.apache.sling.installer.core [12](R 12.0): missing requirement [org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation)] Unresolved requirements: [[org.apache.sling.installer.provider.file [14](R 14.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api)(version>=3.1.2)(!(version>=4.0.0)))]

at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149)

at org.apache.felix.framework.Felix.startBundle(Felix.java:2119)

at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)

at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

at java.base/java.lang.Thread.run(Thread.java:835)

25.07.2019 11:44:11.200 *INFO* [FelixStartLevel] org.apache.sling.javax.activation BundleEvent RESOLVED

25.07.2019 11:44:11.251 *INFO* [FelixStartLevel] org.apache.sling.javax.activation BundleEvent STARTING

25.07.2019 11:44:11.253 *INFO* [FelixStartLevel] org.apache.sling.javax.activation BundleEvent STARTED

25.07.2019 11:44:11.255 *ERROR* [FelixDispatchQueue] org.apache.sling.launchpad.installer FrameworkEvent ERROR (org.osgi.framework.BundleException: Unable to resolve org.apache.sling.launchpad.installer [16](R 16.0): missing requirement [org.apache.sling.launchpad.installer [16](R 16.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api.event)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.sling.installer.core [12](R 12.0): missing requirement [org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation)] Unresolved requirements: [[org.apache.sling.launchpad.installer [16](R 16.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api.event)(version>=1.0.0)(!(version>=2.0.0)))])

org.osgi.framework.BundleException: Unable to resolve org.apache.sling.launchpad.installer [16](R 16.0): missing requirement [org.apache.sling.launchpad.installer [16](R 16.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api.event)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve org.apache.sling.installer.core [12](R 12.0): missing requirement [org.apache.sling.installer.core [12](R 12.0)] osgi.wiring.package; (osgi.wiring.package=javax.annotation)] Unresolved requirements: [[org.apache.sling.launchpad.installer [16](R 16.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.sling.installer.api.event)(version>=1.0.0)(!(version>=2.0.0)))]

at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149)

at org.apache.felix.framework.Felix.startBundle(Felix.java:2119)

at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)

at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

at java.base/java.lang.Thread.run(Thread.java:835)

25.07.2019 11:44:11.257 *INFO* [FelixStartLevel] org.apache.sling.settings BundleEvent RESOLVED

25.07.2019 11:44:11.258 *INFO* [FelixStartLevel] org.apache.sling.settings BundleEvent STARTING

25.07.2019 11:44:11.262 *INFO* [FelixStartLevel] org.apache.sling.settings.impl.SlingSettingsServiceImpl Read Sling ID 75aefd32-fa62-4ec9-ab51-c2253e7f2aed from file C:\Work\Adobe AEM\AEM\crx-quickstart\launchpad\felix\bundle17\data\sling.id.file

25.07.2019 11:44:11.281 *INFO* [FelixStartLevel] org.apache.sling.settings.impl.SlingSettingsServiceImpl Active run modes: [s7connect, crx3, author, samplecontent, crx3tar]

25.07.2019 11:44:11.281 *INFO* [FelixStartLevel] org.apache.sling.settings Service [Apache Sling Settings Service,20, [org.apache.sling.settings.SlingSettingsService]] ServiceEvent REGISTERED

25.07.2019 11:44:11.283 *INFO* [FelixStartLevel] org.apache.sling.settings Service [Apache Sling Sling Properties Configuration Printer,21, [org.apache.sling.settings.impl.SlingPropertiesPrinter]] ServiceEvent REGISTERED

25.07.2019 11:44:11.284 *INFO* [FelixStartLevel] org.apache.sling.settings Service [Apache Sling Sling Settings Configuration Printer,22, [org.apache.sling.settings.impl.SlingSettingsPrinter]] ServiceEvent REGISTERED

25.07.2019 11:44:11.287 *INFO* [FelixStartLevel] org.apache.sling.settings Service [org.apache.sling.settings.impl.SlingSettingsServiceImpl,23, [org.osgi.service.cm.ManagedService]] ServiceEvent REGISTERED

25.07.2019 11:44:11.287 *INFO* [FelixStartLevel] org.apache.sling.settings BundleEvent STARTED

25.07.2019 11:44:11.287 *INFO* [FelixStartLevel] slf4j.api BundleEvent STARTING

25.07.2019 11:44:11.287 *INFO* [FelixStartLevel] slf4j.api BundleEvent STARTED

25.07.2019 11:44:11.287 *INFO* [main] org.apache.felix.framework BundleEvent STARTED

25.07.2019 11:44:11.288 *INFO* [FelixDispatchQueue] org.apache.felix.framework Startup finished in 2262ms

25.07.2019 11:44:11.289 *INFO* [FelixDispatchQueue] org.apache.felix.framework Service [Apache Sling Startup Service,24, [org.apache.sling.launchpad.api.StartupService]] ServiceEvent REGISTERED

25.07.2019 11:44:11.292 *INFO* [FelixDispatchQueue] org.apache.felix.framework FrameworkEvent STARTED

Views

8.2K

Replies

22

Total Likes

Translate
22 Replies
Jörg_Hoh
Employee
Employee
‎25-07-2019 10:09 PDT

Which logfile have you posted? Can you check the error.log file for a hopefully more meaningfull error? Can you reach "localhost:4502" with a browser?

Views

7.5K

Replies

0

Total Likes

Translate
hamidk92094312
Employee
Employee
‎25-07-2019 10:26 PDT

1. Can you post the output of java -version ?

2. Are you running quickstart as root/admin ?

Views

7.5K

Replies

16

Total Likes

Translate
bb2j3z2x
Level 2
Level 2
‎25-07-2019 10:51 PDT
In response to hamidk92094312

java version "1.8.0_221"

Java(TM) SE Runtime Environment (build 1.8.0_221-b11)

Java HotSpot(TM) 64-Bit Server VM (build 25.221-b11, mixed mode)

It's using the JDK in

C:\Program Files\Java\jdk1.8.0_221

Views

7.5K

Replies

15

Total Likes

Translate
hamidk92094312
Employee
Employee
‎25-07-2019 11:31 PDT
In response to bb2j3z2x

Your JDK seems alright.

Can you provide the command/script you used to run the .jar file ?

Views

7.5K

Replies

14

Total Likes

Translate
bb2j3z2x
Level 2
Level 2
‎25-07-2019 12:01 PDT
In response to hamidk92094312

I am just double clicking on the jar file (AEM_6.4_Quickstart.jar) in windows 10.   

I looked at starting it at the command prompt.  And was trying this:

java -XX:MaxPermSize=256m -Xmx1024M -jar AEM_6.4_Quickstart.jar

But nothing was starting outside of the command prompt.   Didn't the AEM box from my screenshot nor anything in the browser.

Not sure if I need to rename the jar file before double clicking.

Views

7.5K

Replies

13

Total Likes

Translate
hamidk92094312
Employee
Employee
‎25-07-2019 12:05 PDT
In response to bb2j3z2x

Can you do the following:

- change the name of the .jar file (assuming its an author environment) > aem64-author-p4564.jar

- run the command > java -jar -Xmx4G aem64-author-p4564.jar

Views

7.5K

Replies

12

Total Likes

Translate
bb2j3z2x
Level 2
Level 2
‎25-07-2019 12:20 PDT
In response to hamidk92094312

I get this:

C:\Work\Adobe AEM\AEM>java -jar -Xmx4G aem64-author-p4564.jar

Loading quickstart 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 3641 MB, meets our expectation of 1024 MB +/- 20

Setting properties from filename 'C:/Work/Adobe AEM/AEM/aem64-author-p4564.jar'

Option '-quickstart.server.port' set to '4564' from filename aem64-author-p4564.jar

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

Redirecting stdout to C:\Work\Adobe AEM\AEM\crx-quickstart\logs\stdout.log

Redirecting stderr to C:\Work\Adobe AEM\AEM\crx-quickstart\logs\stderr.log

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

But nothing starts outside of the command prompt.

Views

7.5K

Replies

11

Total Likes

Translate
hamidk92094312
Employee
Employee
‎25-07-2019 12:34 PDT
In response to bb2j3z2x

you should lower the -Xmx

use this command > java -jar -Xmx1024m aem64-author-p4564.jar

Note: if your machine does not have a good hardware spec it may take up to a couple min for the page to come up.

Views

7.5K

Replies

10

Total Likes

Translate
bb2j3z2x
Level 2
Level 2
‎25-07-2019 12:53 PDT
In response to hamidk92094312

same result...  nothing comes up.

C:\Work\Adobe AEM\AEM>java -jar -Xmx1024m aem64-author-p4564.jar

Loading quickstart 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]

**** WARNING: insufficent heap memory ******************************************

The JVM reports 910 MB but we recommend at least 1024 MB +/- 20

Use your JVM's heap size option (like -Xmx1024M) to set that size.

Will fork a JVM to get enough memory.

********************************************************************************

Available memory below specified limits and low-memory action set to fork, will fork to get enough memory

Preparing to fork JVM, OS name=Windows 10, isWindows=true

Forking JVM: [C:\Program Files\Java\jre1.8.0_221\bin\java.exe, -Xmx1024m, -XX:MaxPermSize=256m, -jar, C:/Work/Adobe AEM/AEM/aem64-author-p4564.jar, -nofork, -pt, CHILD]

Loading quickstart 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]

**** WARNING: insufficent heap memory ******************************************

The JVM reports 910 MB but we recommend at least 1024 MB +/- 20

Use your JVM's heap size option (like -Xmx1024M) to set that size.

Will fork a JVM to get enough memory.

********************************************************************************

Available memory below specified limits and low-memory action set to fork, will fork to get enough memory

Not forking JVM as -nofork option is set

Setting properties from filename 'C:/Work/Adobe AEM/AEM/aem64-author-p4564.jar'

Option '-quickstart.server.port' set to '4564' from filename aem64-author-p4564.jar

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

Redirecting stdout to C:\Work\Adobe AEM\AEM\crx-quickstart\logs\stdout.log

Redirecting stderr to C:\Work\Adobe AEM\AEM\crx-quickstart\logs\stderr.log

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

My laptop is pretty decent.

OS Name Microsoft Windows 10 Pro

Installed Physical Memory (RAM) 32.0 GB

Processor Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz, 2904 Mhz, 6 Core(s), 12 Logical Processor(s)

Hard Disk: 952 GB (730 GB free)

Views

6.9K

Replies

9

Total Likes

Translate
hamidk92094312
Employee
Employee
‎25-07-2019 12:56 PDT
In response to bb2j3z2x

If you are connected to this machine as admin then the last thing that I can think of is that the .jar file is somehow corrupted. 

Views

6.9K

Replies

8

Total Likes

Translate
bb2j3z2x
Level 2
Level 2
‎25-07-2019 13:18 PDT
In response to hamidk92094312

Sorry, nevermind... it started to work.    It just took a really long time to load.    Also that screen doesn't come up, it just goes straight to the browser.    Thanks for all of your help.

Views

6.9K

Replies

7

Total Likes

Translate
bb2j3z2x
Level 2
Level 2
‎02-08-2019 08:37 PDT
In response to bb2j3z2x

Any way to get the quickstart.jar to work by just double clicking on it?  Command line works.   When I double click the jar file,  the quickstart window loads with the on/off switch but when the browser launches, http://localhost:4564/  is in the address bar.

This site can’t be reached

localhost refused to connect.

ERR_CONNECTION_REFUSED

Views

6.9K

Replies

3

Total Likes

Translate
Jörg_Hoh
Employee
Employee
‎03-08-2019 05:15 PDT
In response to bb2j3z2x

have you configured your AEM instance to listen on port 4564? The default for authoring is 4502.

Views

6.9K

Replies

2

Total Likes

Translate
bb2j3z2x
Level 2
Level 2
‎03-08-2019 18:11 PDT
In response to Jörg_Hoh

I tried changing the file name to use port 4502 so it's aem64-author-p4502.jar now, still getting the same result when double clicking,     Not able to view the site.    However doing the same methods from the command line works.    It's fine for now as I can use AEM, but would prefer to just double click on the jar to get it to work.

Views

6.9K

Replies

1

Total Likes

Translate
Jörg_Hoh
Employee
Employee
‎05-08-2019 00:01 PDT
In response to bb2j3z2x

starting via command line (using crx-quickstart/bin/start) is using a totally different approach to launch AEM than the double-click on the quickstart.jar file. For the case of double-click you need to change the filename of the quickstart.jar to change the port, while for the start script you need to customize that.

My personal preference is always to use the start script anyway, because the settings are much more explicit.

Views

6.9K

Replies

0

Total Likes

Translate
Aryan12345
Level 3
Level 3
‎06-12-2019 11:48 PST
In response to bb2j3z2x

I am having the same problem with AEM 6.4 on Win 10 with Java 8. Can you let me know how long it took for you?

Also my log keeps showing this.

07.12.2019 01:14:07.527 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 183

07.12.2019 01:14:22.528 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 184

07.12.2019 01:14:37.529 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 185

07.12.2019 01:14:52.529 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 186

07.12.2019 01:15:07.535 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 187

07.12.2019 01:15:22.536 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 188

07.12.2019 01:15:37.538 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 189

07.12.2019 01:15:52.538 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 190

07.12.2019 01:16:07.545 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 191

07.12.2019 01:16:22.545 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 192

07.12.2019 01:16:37.546 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 193

07.12.2019 01:16:52.546 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 194

07.12.2019 01:17:07.547 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 195

07.12.2019 01:17:22.548 *INFO* [PayloadMap Cache Updater Thread] com.adobe.granite.workflow.core.PayloadMapCache No index available yet for workflowDataLucene. Attempt: 196

Any idea whats happening?

Views

6.9K

Replies

2

Total Likes

Translate
Aryan12345
Level 3
Level 3
‎06-12-2019 21:44 PST
In response to Aryan12345

AEM 6.4 on windows 10 with JDK 8 seems to have a lot of issues in coming up. Replicated the issue in 2 seperate machines.

Also is there a way to get AEM 6.4 working on JDK 10 or 11?

Views

6.9K

Replies

0

Total Likes

Translate
Jörg_Hoh
Employee
Employee
‎07-12-2019 10:23 PST
In response to Aryan12345

This is a totally different issue. Can you please raise a new thread here in the forum?

Thanks,

Jörg

Views

6.9K

Replies

0

Total Likes

Translate
SonDang
Employee
Employee
‎25-07-2019 10:51 PDT

Look like you are using the JRE instead of the JDK. You might want to check Java version that is installed.

Views

7.5K

Replies

0

Total Likes

Translate
santhosh_kumark
Community Advisor
Community Advisor
‎07-12-2019 22:55 PST

Increase the heap memory size to >1024 MB

Try running the below command from the command prompt with verbose option set.

java -Xmx1536M -jar AEM_6.4_Quickstart.jar -v

Hope this helps.

Views

1.5K

Replies

0

Total Likes

Translate