Hi Bill,

It looks like this is happening in your new code. If you can get this to repro when running in a debugger, setting an exception breakpoint on NullPointerException will make it so that you can check out the problem when it happens.

I do have one guess as to the root problem, though. If you're causing the web server to redeploy the webapp (by deploying a new build without restarting the server, either by building it or copying in the files), I've seen problem where sometimes Tomcat is unable to load ClassLoader resources without restarting the whole Tomcat process. The only workaround that I know is to restart the server - it's annoying but typically only a problem on development machines where you're rebuilding.

Thanks,
Josh