


bb2j3z2x
bb2j3z2x
25-07-2019
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)
hamidk92094312
Employee
hamidk92094312
Employee
25-07-2019
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.
bb2j3z2x
bb2j3z2x
25-07-2019
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.
bb2j3z2x
bb2j3z2x
02-08-2019
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.
localhost refused to connect.
Jörg_Hoh
Employee
Jörg_Hoh
Employee
03-08-2019
have you configured your AEM instance to listen on port 4564? The default for authoring is 4502.
bb2j3z2x
bb2j3z2x
03-08-2019
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.
Jörg_Hoh
Employee
Jörg_Hoh
Employee
05-08-2019
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.
Aryan12345
Aryan12345
06-12-2019
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?
Aryan12345
Aryan12345
06-12-2019
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?
Jörg_Hoh
Employee
Jörg_Hoh
Employee
07-12-2019
This is a totally different issue. Can you please raise a new thread here in the forum?
Thanks,
Jörg