Restricting the size of configuration and extended objects
Use this procedure to limit the number of records that a server can provide to an Application Server for a single configuration object or extended object. Processing large numbers of records for a configuration object or extended object can consume large quantities of memory, particularly when the Application Server processes multiple configuration objects or extended objects on multiple servers simultaneously. Using this procedure can help prevent the Application Server from running out of memory.
Configuration objects and extended objects can be used in component templates, Audit, Snapshot, and Compliance Jobs, and in live browsing. If a job targets a server that returns more records for a configuration object or extended object than the limit set in this procedure, the job fails on that server with a parsing error.
- Start the Application Server Administration console, as described in Starting the Application Server Administration console.
- To limit the number of records that an Application Server can process for a single configuration object or extended object, enter the following:
set AssetThresholds MaxConfigRecords #
where # is the maximum number of records to be processed. By default, this value is set to 50,000. Setting this value to 0 means no records are processed.
- Restart the Application Server.