Posts tagged "pageSize"

LiveCycle Workbench ES: OutOfMemoryError when working with many LC7 QPACs

Issue

 When opening Workbench after migrating from LC7, or after manually deploying many LC7 QPACs in the LC7.x components view, you may receive the following error:

Caused by: java.lang.OutOfMemoryError: Java heap space ; nested exception is:   
java.lang.OutOfMemoryError: Java heap space   
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)   
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)   
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationConte xt.java:1087)   
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)   

This may be accompanied with internal errors in Workbench, or other memory warnings and messages.

Reason

 The OutOfMemoryError occurs as the server is loading all of the LC7 component configurations at the same time and sending all of this information to the Workbench client.  It cannot handle this amount of data at one time, and so, throws the memory errors.  The server may also be hitting some memory limitations depending on the heap size and platform (i.e. weblogic uses a lot more RAM than JBoss).

Solution

 This issue has been fixed in Workbench ES 8.2.1.3 and later versions.  There is a patch available for both the server and workbench 8.2.1.2.  You should contact Adobe support if you require this patch.

The patch will expose a new parameter in the workbench.ini file to control the pageSize for the communication between the LiveCycle server and Workbench.  You can check this parameter in <Workbench_Home>/Workbench/workbench.ini.  The parameter should be set to 3 to resolve the OOM situation:
-Dcom.adobe.workbench.lc7component.pageSize=3
After making any such changes to the configuration of Workbench you may need to start Workbench cleaning out the temp files.  You can do this by starting Workbench from the command line from the directory listed above using the -clean console command line switch.

You should also try increasing the JVM heap size for both the server and Workbench, and run Workbench on a separate machine to the LiveCycle server, if you are not already doing so.

 reference: (180896059/2325722)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)