-
Notifications
You must be signed in to change notification settings - Fork 58
Known Issues
Bertrand de Coatpont edited this page May 24, 2016
·
9 revisions
- If you have another version of ANT installed on your system, you can certainly use it also. However, make sure your ${antroot}/ant/lib folder contains the ant-contrib-1.0b3.jar file contained in the demo machine as it provides support for some extensions used by the Demo Machine main build.xml file
- AEM instances might not start if you have a ulimit setting in your .bash_profile like so: "ulimit -n 1024". This setting is recommended when you have issues with a large number of files open in IntelliJ. However, this causes an issue with AEM which requires the ulimit to be 8192. Change the setting in the .bash_profile file to now become "ulimit -n 8192", restart Terminal and demomachine works like a charm
- If you have other AEM instances already running on your system, the demo machine will not be able to stop/start them, hence you will have to stop them manually before installing a new demo environment
- If AEM is not starting properly, make sure you are using a 64bits JDK/JRE on your system (you can use the Demo Machine "Diagnostics" menu option to make sure, check the sun.arch.data.model property, it should be 64 (not 32)