You can increase the VM arguments, on %PUBLISHER_INSTALL_DIR%\publisher.ini, like:
-startup
plugins/org.eclipse.equinox.launcher_1.5.700.v20200207-2156.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.1200.v20200508-1552
-clean
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=@user.home/rhp2md-workspace
-Xms256m
-Xmx10g
-Drhapsody.omroot=S:
-Drhp2md.graphical.properties.path=C:\ProgramData\Publisher4Rhapsody\3.1.0\display.properties
-Drhp2md.publisher.properties.path=C:\ProgramData\Publisher4Rhapsody\3.1.0\publisher.properties
Note 1: The values to set depend on the specifications of the system you are working on. If this is not enough, you could try to increase again the Xmx value.
Note 2: Values can be managed when installing Publisher for Rhapsody.
If you have this kind of error, it means that there is a compatibility issue between Java, Rhapsody and the Publisher.
If Publisher for Rhapsody seems to have been running in a vacuum for a long time, a problem may have arisen.
We have developed a problem management process which you will find in the section Troubleshooting Publisher for Rhapsody.
Publisher for Rhapsody has been validated with Rhapsody 8.3.1, 8.4 and 9.0.2.
Older versions of Rhapsody are not supported.
To obtain the license information needed, run FlexNet LMTools GUI.
Select System Settings tabulation, then Save HOSTID info to a File by clicking the corresponding button.
Provide the generated file to the support team.
Custom Stereotypes are transformed.
Structure of Elements between Rhapsody and Cameo is kept.
Yes.
There are several containment patterns that are not supported by Rhapsody. For example, an Activity cannot own another Activity. To avoid the loss of data, the containment tree is modified to keep the data at the end of the publication. Check Modeling Guidelines for more information