Macromedia live cycle 7.2 매뉴얼
Adobe LiveCycle
Enhancing Server Performance
Installing and Configuring LiveCycle Security Products for JBoss
Cleaning up temporary files from Global storage directory 74
Example B.1
Calculating the JVM maximum heap size
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 ten jobs are run simultaneously, and each job
has nine input files and one result file (a total of ten files per job, and 1000 files processed simultaneously).
All of the files are under 512 KB in size.
The server needs to be configured for the scenario where ten jobs are run simultaneously, and each job
has nine input files and one result file (a total of ten files per job, and 1000 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 51.2 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 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
OutOfMemoryError even when sufficient total free space exists.
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
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.
OutOfMemoryError can occur even though the JVM maximum heap size has been adjusted for an increase
in maximum inline size.
and the garbage collector is unable to compact the heap sufficiently to regain large blocks of free space.
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.
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 from Global storage directory
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.
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.