My Web Start launched app hit a major hitch when my customers upgraded to u91 this week. All of the sudden, an app that used to take less than one minute to load and start now takes about 20 minutes. Then it runs super slow. Upon inspection with the console, I discovered that Web Start is attempting to locate EVERY SINGLE CLASS from a (non-existent) cache on my website instead of simply using the jars indicated by the jnlp file. I get thousands of messages similar to the following:
network: Connecting https://mysite.com/cert/login/com/mysite/view/DrawingImage$ColoredPolygon.class with proxy=DIRECT
network: Connecting socket://mysite.com:443 with proxy=DIRECT
network: Cache entry not found [url: https://mysite.com/cert/support_jars/com/mysite/view/DrawingImage$ColoredPolygon.class, version: null]
And not just for each of my classes, but to make matters much worse, also for each and every jre class -- for example:
network: Connecting https://mysite.com/cert/login/org/jnp/interfaces/NamingEvents.class with proxy=DIRECT
network: Connecting socket://mysite.com:443 with proxy=DIRECT
network: Cache entry not found [url: https://mysite.com/cert/login/org/jnp/interfaces/NamingEvents.class, version: null]
When I revert to u77, this does not happen.
Has anyone else hit this issue? Is there something I need to change in the jar manifests or the jnlp (something that didn't used to be required)? I find no clues in the release notes for u91.
link to jnlp: http://getmoremath.com/cert/login/launch.jnlp
I'm looking for a workaround (other than simply telling all my customers to avoid getting u91, or to uninstall if they did). Any pointers would be welcome. Thanks!
Josh Britton