Maybe someone can help me out with this issue. Every time we run a regular scan of our web application, the scan gets about half way through it's tests and then the servers it is testing hang up and require tomcat restart to get them back functioning. I;m not sure what could be causing this issue. I assume that the memory on those servers is just getting completely occupied and utilized until it just has nothing left to run. Any ideas on AppScan setting I can look into or change that might help with this issue? anyone else had this issue before?
Pinned topic Running a scan causes servers to stop functioning.
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-09T01:05:16Z at 2013-02-09T01:05:16Z by SystemAdmin
Re: Running a scan causes servers to stop functioning.2013-02-04T07:55:08ZThis is the accepted answer. This is the accepted answer.Hello,
You could check and revise your Test Policy. Some of the invasive tests will attempt to "break" your web server (execute particular commands, saturate memory, shut it down etc.). This is, of course, intentional (if AppScan can do it, hackers can do it too) so once you take note of this sort of vulnerability, you can disable this test in your test policy, allowing the other tests to complete.
If this does not help, you can contact AppScan Support for a more in-depth analysis of the issue.
Hope this helps - regards, Marek
Re: Running a scan causes servers to stop functioning.2013-02-09T01:05:16ZThis is the accepted answer. This is the accepted answer.If you search in Google for "appscan large site" You will find a number a articles on how to manage large scans.
These may be of interest: