Troubleshooting¶

NSIA Runs Out of Memory¶

• Reduce the rate of the scans (this is preferred)
• Increase the amount of memory available to NSIA

Note that NSIA has a limit on the maximum amount of memory that it will use which is independent of the amount of memory that the server it if running on has. In other words, NSIA may be running out of memory even though the server has plenty of available memory. The maximum limit can be modified by changing the Java settings

Reducing the Scan Rate¶

To reduce the scan rate, select one of the rules and reduce the scan frequency. Additionally, you can reduce the number of resources to be scanned by lowering the depth or resource limit on HTTP Auto-Discovery rules. However, note that reducing the number of resources to scan reduces the chance that NSIA will detect a security problem. Generally, it is better to increase the amount of memory available or reduce the scan frequency.

Increasing Memory¶

The Java Runtime Environment contains a setting that limits how much memory the application uses. To increase this value, edit the config.ini file and change the value of the JVM.Arguments option. The value of the argument should be "-Xmx" followed by the amount of mamoery you want allocated to the JRE. Below is a sample of a config.ini file that allocates up to 2 GB:

JVM.Arguments=-Xmx2g