IBM E02HRLL-G Administration Guide - Page 165
Avoiding long processing time for large encrypted documents, Avoiding out-of-memory errors, Document
![]() |
View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 165 highlights
2. Follow the steps in the ″"Avoiding out-of-memory errors" to increase memory size and speed up processing of encrypted documents. Avoiding long processing time for large encrypted documents Large files can be compressed before sending. Large file support with an order of size in GBs has been extended for AS2 and AS3. In version 6.2, the maximum file size processed using byte arrays is configurable. When the amount of memory allocated is more than the available heap size, OutOfMemoryError occurs. If the size of data is less than the available memory, OutOfMemoryError may still occur if the memory allocated increases available memory. You can specify the maximum file size that can be used with byte arrays using the property bcg.maximumFileSizeForByteArrays. If the file size is more than the value of this property, it is processed using streams. If the file size is less than the value of this property, and if sufficient memory is not available, an error event BCG210050 is generated. When you log in as a hub operator, navigate to System Administration tab > Common Attributes tab. Overwrite the default value of bcg.maximumFileSizeForByteArrays property to specify the maximum file size to be used with byte arrays. Increase the value of this property for better performance. To avoid out of memory errors, the value of property bcg.maximumFileSizeForByteArrays must be set such that very large files are processed using streams rather than as byte arrays. For example, if RAM size is 512 MB, then the value of bcg.maximumFileSizeForByteArrays property can be set to 20 MB. All documents of size greater than 20 MB will be processed using streams and not using byte arrays. Documents of size less than 20 MB will be processed in memory. Avoiding out-of-memory errors Areas that can contribute to the out of memory conditions are: v Document Manager memory configuration This configuration specifies the amount of memory the underlying Java application has allocated to work with. v Document Manager workload You can configure the number of threads subcomponents can use. If the configured thread number is high and there is a heavy work load then more memory is required to handle all of the documents. v Document structure of the documents that are being processed Depending on the document structure more memory can be required to process a document, especially for large documents. Areas affected are security (encryption, decryption, signing, signature verification) and XML Transformation and Validation processing steps (especially those documents with large text values). For more information on OutOfMemoryError due to large file size, see "Avoiding long processing time for large encrypted documents." Document Manager memory configuration About this task To improve performance and avoid out of memory errors, you can increase the size of the initial and maximum heap sizes for the Websphere Partner Gateway components. From the Websphere Application Server admin console: 1. Navigate to Application Servers. Chapter 17. Troubleshooting 159
![](/manual_guide/products/ibm-e02hrllg-administration-guide-f948001/165.png)