-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b31
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2222346 | 7u6 | Nam Nguyen | P3 | Closed | Fixed | b03 |
JDK-2222239 | 7u4 | Nam Nguyen | P3 | Closed | Fixed | b17 |
- Turn on tracing level all.
- Run webstart an application with applet-desc having <update check='background'/> with lazy jars that would not be downloaded until after the application started.
- Update the lazy jar, make sure to touch it so timestamp change.
- Observe in tracing file double starting of LDUpdater and double downloading of same lazy jar:
network: LDUpdater: started background update check
...
network: LDUpdater: started background update check
...
network: Background Update Thread: update cache: http://javaweb/~ntnguyen/tests/check-always-lazy-update/lib/MyUtil.jar
...
network: Background Update Thread: update cache: http://javaweb/~ntnguyen/tests/check-always-lazy-update/lib/MyUtil.jar
...
- Run webstart an application with applet-desc having <update check='background'/> with lazy jars that would not be downloaded until after the application started.
- Update the lazy jar, make sure to touch it so timestamp change.
- Observe in tracing file double starting of LDUpdater and double downloading of same lazy jar:
network: LDUpdater: started background update check
...
network: LDUpdater: started background update check
...
network: Background Update Thread: update cache: http://javaweb/~ntnguyen/tests/check-always-lazy-update/lib/MyUtil.jar
...
network: Background Update Thread: update cache: http://javaweb/~ntnguyen/tests/check-always-lazy-update/lib/MyUtil.jar
...
- backported by
-
JDK-2222239 webstart start 2 background update threads resulted in double downloads of same jars
-
- Closed
-
-
JDK-2222346 webstart start 2 background update threads resulted in double downloads of same jars
-
- Closed
-