-
Bug
-
Resolution: Fixed
-
P1
-
6u10
-
b21
-
b21
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2199243 | 7 | Thomas Ng | P1 | Closed | Fixed | b64 |
I tried last night build, and there is still problem with java web start.
I tried running the association test case, excessive relaunch is gone, but I found 3 problems by looking at the trace:
http://nicole1.sfbay.sun.com:8080/JavawsMustangIntegTest/association/association_test_un_signed.jnlp
1. We are always trying to download .pack.gz , even for .jnlp file. But the jnlp file does not have jnlp.packEnabled set.
2. The above webserver seems to always return 200 for update check, so each time a new download is done. But looks like we are not removing/invalidating previous cache entry, after we downloaded a new cache entry.
I tried running the association test case, excessive relaunch is gone, but I found 3 problems by looking at the trace:
http://nicole1.sfbay.sun.com:8080/JavawsMustangIntegTest/association/association_test_un_signed.jnlp
1. We are always trying to download .pack.gz , even for .jnlp file. But the jnlp file does not have jnlp.packEnabled set.
2. The above webserver seems to always return 200 for update check, so each time a new download is done. But looks like we are not removing/invalidating previous cache entry, after we downloaded a new cache entry.
- backported by
-
JDK-2199243 cache entry update is broken
-
- Closed
-