Troubleshooting

Common Installation Issues:

To troubleshoot, do the following:

  • Double check that you have at least Java version 1.6 installed.
  • Try a context menu (usually right-mouse click) on the AEM WCM Quickstart, and select “Open With….”
  • Check if Java or Sun Java is listed, and try to run AEM WCM with it. If you have multiple Java versions installed, select the supported one.

    If you succeed with this step, and your operating systems offers an option to always use the selected program to run the .jar files, select it. Double-clicking should work from now on.

  • Sometimes reinstalling the supported Java version helps restore the correct association.
  • You can always run CRX using the command line or start/stop scripts as described earlier in this document.

CRX throws running out of memory:

CRX itself has a very low memory footprint. If the application running within CRX has bigger memory requirements or requests memory-heavy operations (for example, large transactions), the JVM instance where CRX runs needs to be started with appropriate memory settings.

Use Java command options to define memory settings of the JVM (for example, java -Xmx512m -jar crx*.jar to set heapsize to 512MB).

To automatically create a heap dump when running out of memory, use the following command:

java -Xmx256m -XX:+HeapDumpOnOutOfMemoryError -jar *.jar

The AEM Welcome screen does not display in the browser after double-clicking AEM Quickstart

In certain situations, the AEM WCM Welcome screens does not automatically display even though the repository itself is successfully running. This may depend on operating system setup, browser configuration, or similar factors.

The usual symptom is that the AEM WCM Quickstart window displays “AEM WCM starting up, waiting for server startup….” If that message displays for a relatively long time, enter the AEM WCM URL into the browser window manually, using the default 4502 port, or the port on which the instance is running: http://localhost:4502/.

Also, logs may reveal the reason for the browser not starting.

Sometimes, the AEM WCM Quickstart window has the message “AEM WCM running on http://localhost:port/” and the browser does not start automatically. In this case, click on the URL in the AEM WCM Quickstart window (it is a hyperlink) or manually enter the URL in the browser.

If everything else fails, check the logs to find out what has happened.

Any Questions?

reach out to techroomweb….

Thanks for reading.

Leave a comment

search previous next tag category expand menu location phone mail time cart zoom edit close