Thanks for the quick response Tim!
We have been scouring the internet for a solution to this and I hope to finally get to the bottom of this issue.
I read your ideas to clear this issue up and I have already tried all but deleting the java-web-start folder contents, so I deleted the sub-folder, restart the domain, redeploy the application and as of right now it seems to be working ok.
I am still very curious how we ended up in this error state to begin with, because we have three separate domains that all reproduced the same issue. I will try to give you a little more background on how the Web Start problems first began.
We first got all our packaging set up for V3 and started testing on a clean install of V3. After a few iterations, we were able to get all of the basic EE functionality working, so we started deploying V3 on a few other servers and upgrading other applications.
As soon as we tested Web Start we found an error related to a ClassNotFound exception on the second launch from any given client. We were able to get one successful launch after clearing out the client cache only to find the error pop up again on the second launch.
We found the only work around to this was changing the clients (Java Control Panel) Advanced\Security\Mixed Code to “disable verification”.
This is turn created the server side NPE described in my first post, which as a result would cause Grizzly / HTTP related problems invoking our Web Services.
I will try to delete that directory on my other application servers and see if the problem comes up again. If there is any testing I could do here to help you figure out the root cause, please let me know.
Thanks!
Todd
[Message sent by forum member 'tmcerwin']
http://forums.java.net/jive/thread.jspa?messageID=478604