Webstart hangs "Checking for latest version" of jnlp file
843802Oct 24 2005 — edited Oct 27 2005I have a simple webstart app consisting of one JNLP file and 3 jars. Java webstart appears to hang if the JNLP file is not new. It deploys fine if the jnlp file is new or if there is no cache, but if the file is not new and should not need to be downloaded the WS screen hangs for a long time with the message in the title, and the CPU hovers around 90%.
I am running java 1.5.0_05-b05, the server is tomcat 5.0.28. The jnlp file is a plain file (i.e. not generated) and I am not using the JNLP download servlet.
adding/removing the href attribute has no effect. I can use the allow-offline to automatically start the app and there is no delay, but it is absolutely necessary that the jars get checked prior to the start of the app, so this is not an option. Plus, the checking still pegs the CPU in the background, and that makes MY app look slow, and this does not appear to be my fault so I don't want it make my app look slow and unresponsive.
Any ideas?