Troubleshooting » History » Version 2
Version 1 (Luke Murphey, 04/03/2010 01:21 PM) → Version 2/8 (Luke Murphey, 04/03/2010 05:38 PM)
h1. Troubleshooting
h2. NSIA Runs Out of Memory
To resolve this either:
* 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
h3. Reducing the Scan Rate
To reduce the scan rate, open the configuration page (i.e. http://127.0.0.1:8080/System/Configuration) and reduce the "Maximum HTTP Scan Threads" setting. By default, the system will allocate 10 threads to scanning at select one time. Reducing the number of threads will reduce the memory rules and CPU usage of reduce the system at any one time.
scan frequency. Additionally, reducing the scan frequency of the individual rules may be necessary to you can reduce the load on the system. Finally, system load can be reduced by decreasing 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, this option should be avoided. it is better to increase the amount of memory available or reduce the scan frequency.
h3. 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:
<pre>
JVM.Arguments=-Xmx2g
</pre>
h2. NSIA Runs Out of Memory
To resolve this either:
* 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
h3. Reducing the Scan Rate
To reduce the scan rate, open the configuration page (i.e. http://127.0.0.1:8080/System/Configuration) and reduce the "Maximum HTTP Scan Threads" setting. By default, the system will allocate 10 threads to scanning at select one time. Reducing the number of threads will reduce the memory rules and CPU usage of reduce the system at any one time.
scan frequency. Additionally, reducing the scan frequency of the individual rules may be necessary to you can reduce the load on the system. Finally, system load can be reduced by decreasing 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, this option should be avoided. it is better to increase the amount of memory available or reduce the scan frequency.
h3. 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:
<pre>
JVM.Arguments=-Xmx2g
</pre>