- Go to <modeling tool installation directory>\bin and open the <modeling tool>.properties file (eg., magicdraw.properties, csm.properties, cameoea.properties) for editing. If you are using modeling tools of version 17.0.4 or earlier, the name of the property file is mduml.properties.
- In the JAVA_HOME line, add the path to the Java software. For example: JAVA_HOME=C\:Program Files\\Java\\jre1.8.0_144
NOTE: Integrated modelling tools runs on the JVM specified by the IDE. In order to change the JVM, you must modify the startup properties for the IDE that the modeling tool integrates with. If you are running the software integrated with IDE, read the appropriate readme.html for specific integration, found in the integrations folder.
Java version 9 is set as the default system Java after updating Java. This Java version is not supported by our modeling tools*.
The solution is to download and install version 18.4 SP1 or a later original signed .dmg file, as it has the required Java version bundled in.
If you are using an earlier version than 18.4 SP1 and cannot start the modeling tool*, please do the following:
- Download the original signed <modeling tool*>.dmg file and install the application again.
- In bin\magicdraw.properties**, set JAVA_HOME to the Java version installed in the <modeling_tool*_installation_directory >\java folder.
Example: JAVA_HOME=/Applications/MagicDraw/jre1.8.0_102/mac/Contents/Home/jre
- Run magicdraw.sh*** file from the /bin folder.
*MagicDraw, Cameo EA, Cameo Systems Modeler
** cameoea.properties, csm.properties
***camocea.sh, csm.sh
You can change the java maximum heap size (-Xmx) in your /bin/mduml.properties* file, in the line:
JAVA_ARGS=-Xmx800M
The maximum theoretical heap limit for the 32-bit JVM is 4G. Due to various additional constraints such as available swap, kernel address space usage, memory fragmentation, and VM overhead, in practice the limit can be much lower. On most modern 32-bit Windows systems the maximum heap size will range from 1.4G to 1.6G. On 32-bit Solaris kernels the address space is limited to 2G. On 64-bit operating systems running the 32-bit VM, the max heap size can be higher, approaching 4G on many Solaris systems.
On 64-bit VMs, you have 64 bits of addressability to work with resulting in a maximum Java heap size limited only by the amount of physical memory and swap space your system provides.
More information about OutOfMemory problems you can find in readme.html by "OutOfMemory problem" paragraph. This file is located in <MagicDraw installation directory>.
* If you are using MagicDraw 17.0.5 or later, the name of the property file is magicdraw.properties.