I have attempted to run ZAP 2.6.0 against the OWASP benchmark (checked out from git as of 30 Jun 2017) but have been unsuccessful so far.
On Windows, ZAP completes its scan but only rates 5% on the scorecard, not the 20% I was expecting. I noticed that there are many Java stack traces generated in the benchmark while the scan is running. Also, the ZAP scan pauses for a long time at 69%, but it does eventually continue. This was on a machine with 32 GB of RAM with Java 1.8.0_131 64-bit installed.
On Red Hat 7.3, the scan gets to 69% and hangs. This was on a VM with 16 GB of RAM, also with Java 1.8.0_131. The benchmark console also shows a bunch of Java stack traces.
In both cases, ZAP and the benchmark were being run on the same machine. Also, I just did the Quick Start Attack, I didn't do any additional configuration.
Is there some special configuration required of ZAP to get it to score 20% on the benchmark?
Why does it hang at 69% on Linux?