Avoiding OutOfMemoryExceptions in LiveCycle Workbench

Workbench ES is LiveCycle ES’ development IDE. It is Eclipse-based and hence is a desktop Java application. Java applications cannot utilize of all of the memory (RAM) available on the desktop unless they are explicitly allowed. This is specified by means of two JVM init arguments, namely -Xms (minimum memory to grab from Windows on startup) and -Xmx (maximum memory to grab if required, and never more).

-Xms and -Xmx can be configured in the workbench.ini file located in %WORKBENCH_INSTALL_ROOT%/Workbench/. If you are a frequent user of the ‘Record and Playback’ feature in Workbench, and if you use process variables in your orchestrations that can potentially hold large documents, the default JVM memory settings will cause OutOfMemoryExceptions. To avoid these, set -Xms and -Xmx to 256 MB and 1024 MB respectively, assuming that your desktop has enough RAM to spare.

1) Stop Workbench
2) Edit workbench.ini and save the changes
3) Start Workbench

Afterwards, the workbench.ini should look something like as follows (only the initial part shown):

#Product Runtime Configuration File

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 3.5/10 (2 votes cast)
Avoiding OutOfMemoryExceptions in LiveCycle Workbench, 3.5 out of 10 based on 2 ratings
This entry was posted in Adobe LiveCycle ES and tagged . Bookmark the permalink.

Comments are closed.