You configuration looks good so far, but there are numerous other considerations...
1. Are you using Administrative Security? If so you may need to specify the username and password of a user who can access the servlet.
2. Verify your SOAP END PORT is correct
If you haven't come across these links, they may offer some assistance:
www.ibm.com/developerworks/websphere/lib...
publib.boulder.ibm.com/infocenter/wasinf...
Regardless of the version of platform you run WebSphere on, the above links should still be accurate. Additionally, the perfServlet hasn't changed much after version WAS version 6, so these links should still be applicable (I'm not positive on WAS 8.0 just yet as I haven't deployed it in my environments.)
You can also try dropping the arguments after /perfservlet to see if you get anything.
Another link worth looking at is: josephamrithraj.wordpress.com/2010/07/08...
The data here is written by Joseph who is another very active GWC member.
You can always try restarting the JVM where your app is deployed. I can't recall if you must restart it after making changes to the virtual host definition.
In my enterprise, I do not leverage the defaulhost definition and instead opt to create a new virtual host for every application. It's personal preference, really, but I find that some applications have additional mime type entries that other applications are not approved to process. By using different virtual host definitions per application I can provide the granularity needed for each application and ensure that each application is served correctly. Again, personal preference here, but this is ideal for me.
Good luck and let us know if the above helps.