Opened 3 years ago
Last modified 3 years ago
#11298 new defect
Extra caching when run under JavaWebStart
| Reported by: | SergeyAstakhov | Owned by: | team |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | tested |
| Keywords: | cache webstart | Cc: | wiktorn |
Description (last modified by )
Since JDK 7 Update 2 they turned on feature of caching any resouces downloading by URLConnection. Quote from doc (http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/enhancements-7.html#javase7u2):
"Caching enabled by default: Caching of network content for application code running in Web Start mode is now enabled by default. This allows application improved performance and consistency with applet execution mode. To ensure the latest copy of content is used, the application can use URLConnection.setUseCaches(false) or request header Cache-Control values no-cache/no-store."
This is lead to two problem (and may be to others):
- Bing attribution data is not updated properly, so new images (when bing updated it) does not displayed in JOSM.
- Imagery tiles is cached twice (in JWS cache and JOSM cache) and just waste disk space and degrade performance.
The first problem is especially troubling.
Can you fix this?
Attachments (1)
Change History (9)
Changed 3 years ago by
| Attachment: | JWSCacheResources.png added |
|---|
comment:1 Changed 3 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 3 years ago by
| Priority: | normal → major |
|---|
comment:3 Changed 3 years ago by
comment:4 Changed 3 years ago by
| Description: | modified (diff) |
|---|---|
| Keywords: | cache webstart added |
comment:5 Changed 3 years ago by
| Cc: | wiktorn added |
|---|
comment:6 follow-up: 7 Changed 3 years ago by
I tried to test it, but I failed on java security refusing to launch unsigned or self-sgined jar. I'd need some walkthrough, how to test it.
Anyway - I'm worried that there is only half-solution to the problem and use URLConnection.setUseCaches(false) but this would also have a negative impact on any CDN-s, caches between user and server, as well as, doesn't guarantee, that JWS will not put those objects into its cache anyway. So imagery will work correct, but disks will be trashed with cache entries.
As far as I've checked, the default value of cache size is 32768MB which is quite a lot...
comment:7 follow-up: 8 Changed 3 years ago by
Replying to wiktorn:
I tried to test it, but I failed on java security refusing to launch unsigned or self-sgined jar. I'd need some walkthrough, how to test it.
I'm not aware of this problem. Could you report it in a separate ticket with status report and screen shot?
See #8904