Policy engines (PEs) can sometimes fail to analyze archives of .jar files or very large .zip files. This is because these items expand in memory and can consume all of a PE's available memory resources. This problem mainly arises when using the FSA to scan many of these files in parallel.
If you experience excessive memory consumption by a PE, we recommend that you reduce the maximum number of concurrent operations, ideally to one or two and at most to the number of physical CPU cores in the PE host server. To do this, you must edit the machine policy for the host server. Specifically, you need to edit the Maximum Number of Concurrent Operations setting; find this in the Policy Engine folder.
|
Copyright © 2014 CA.
All rights reserved.
|
|