Memory Configuration for Virus Scanning of Files Exceeding Scan Buffer Size
Files that exceed the specified scan buffer size require you to plan memory configurations across multiple applications for the expected volume of inbound file load.
For example, if 100 MB is the scan buffer size and you have 10 files of size greater than 100 MB being uploaded concurrently, then 1000 MB of available memory will be used by the virus scanning process. The upload of any additional files will fail because JVM has reached its memory limit. To handle such scenarios, you must consider the following points:
Scan buffer size configured in ActiveTransfer Gateway. In the
Antivirus Scan tab of the
ActiveTransfer Gateway management page, set the
Scan Buffer Size for file data as any one the following:
No value: If you don't define any value here, the default scan buffer size is 100 MB. The default scan buffer size is
Unlimited (that is, zero). This value means
ActiveTransfer Gateway retains the whole file in-memory while scanning is in progress.
0. Set this value for
ActiveTransfer Gateway to accept unlimited file buffer size.
Software AG does not recommend the use of
0 because it could consume all the available memory.
Limited scan buffer size: You can specify any scan buffer size other than zero.
File size configured in the ICAP server. When configuring the ICAP server, ensure that the ICAP server supports the maximum file size you expect to receive. For example, if you set the maximum file size as 80 MB, and the file received is 100 MB, the virus scan result might not be accurate. ICAP might report that the file is virus-free despite the file being infected.
For recommendations on optimal configuration of your ICAP server, see the ICAP server documentation.
JVM memory configured in Integration Server. When configuring for antivirus, ensure that the JVM size is considerably larger than the scan buffer size you set for inbound files in
ActiveTransfer Gateway.
If a file size exceeds the JVM memory limits, file upload fails.
