Cleaning Up Temporary Files In The Global Storage Directory; Db2 Configuration Settings - Adobe LIVE CYCLE 7.2 - INSTALLING AND CONFIGURING LIVECYCLE FOR JBOSS Manual

Adobe LiveCycle
Installing and Configuring LiveCycle for JBoss
Example F.1
In this example, the current JVM maximum heap is set to 512 MB and the maximum inline size is 64 KB. The
server needs to be configured for the scenario where 10 jobs are run simultaneously, and each job has 9
input files and 1 result file (a total of 10 files per job, and 100 files processed simultaneously). All of the files
are under 512 KB in size.
To store all of the files inline, the maximum inline size must be set to at least 512 KB.
The required increase in the JVM maximum heap size is calculated using the following equation:
(512 KB) x (100) = 51200 KB, or 512 MB
The JVM maximum heap size must be increased by 512 MB for a total of 1GB.
Considering heap fragmentation
Setting the size of inline documents to large values raises the risk of an OutOfMemoryError on systems
that are prone to heap fragmentation. To store a document inline, there must be sufficient contiguous
space in the JVM heap memory. Some operating systems, JVMs, and garbage collection algorithms are
prone to heap fragmentation. Fragmentation decreases the amount of contiguous heap space, and can
lead to an OutOfMemoryError even when sufficient total free space exists.
For example, previous operations on the application server have left the JVM heap in a fragmented state,
and the garbage collector is unable to compact the heap sufficiently to regain large blocks of free space.
An OutOfMemoryError can occur even though the JVM maximum heap size has been adjusted for an
increase in maximum inline size.
To account for heap fragmentation, the inline document size must not be set higher than 0.1% of the total
heap size. For example, a JVM maximum heap size of 512 MB can support a maximum inline size of 512 MB
x 0.001 = 0.512 MB, or 512 KB.

Cleaning up temporary files in the Global storage directory

When a workflow process is executed, temporary files are placed in the Global storage directory, but are
not deleted when the process is complete. These files are placed under subdirectories with the name,
Session[NNNN], where NNNN is the workflow process ID. To prevent running out of disk space, you must
regularly remove the Session directories associated with fully completed processes.
If the Global storage directory is not set explicitly in Configuration Manager, the default location of the
Global storage directory is [TempDir]/AdobeDocumentStorage/global. If [TempDir] is also not specified by
the user in Configuration Manager, the default location is java.io.tmpdir.

DB2 configuration settings

If you are running LiveCycle Form Manager with a DB2 database and the computer stops responding,
check the server log files for deadlock-related messages. If you see such messages in the log files, change
your DB2 configuration parameters. Set the LOCKTIMEOUT parameter to 15, and double the values for the
APPLHEAPSZ, STMTHEAP, and SORTHEAP parameters. You must then restart the database and application
server.
Calculating the JVM maximum heap size
Cleaning up temporary files in the Global storage directory
Enhancing Server Performance
118