JDK-6898702 : REGRESSION: Failed to recover corrupted cache entry
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6u18
  • Priority: P2
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2009-11-05
  • Updated: 2010-04-26
  • Resolved: 2009-11-19
Description
Installed update 18 today and first  got this:\
(This is reformatted from a custom logger)\
\
02:41:26[00002:-5] dsi.client.module.StartupInitializer.run(StartupInitializer.java:107)ERROR: Failed to recover corrupt cache entry\
---- 1 ---- Throwable - Class (class java.lang.RuntimeException) V(4.06.-01) ----\
	---- Message (ERROR: Failed to recover corrupt cache entry) ----\
	at com.sun.deploy.cache.CacheEntry.recover(Unknown Source)\
	at com.sun.deploy.cache.CacheEntry.getManifest(Unknown Source)\
	at com.sun.deploy.cache.CachedJarFile.getManifest(Unknown Source)\
	at sun.misc.URLClassPath$JarLoader$2.getManifest(Unknown Source)\
	at java.net.URLClassLoader.defineClass(Unknown Source)\
	at java.net.URLClassLoader.access$000(Unknown Source)\
	at java.net.URLClassLoader$1.run(Unknown Source)\
	at java.security.AccessController.doPrivileged(Native Method)\
	at java.net.URLClassLoader.findClass(Unknown Source)\
	at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source)\
	at java.lang.ClassLoader.loadClass(Unknown Source)\
	at java.lang.ClassLoader.loadClass(Unknown Source)\
	at dsi.joint.io.DConnect.<init>(DConnect.java:62)\
	at dsi.client.module.StartupInitializer.createServerURL(StartupInitializer.java:125)\
	at dsi.client.module.StartupInitializer.run(StartupInitializer.java:85)\
	at java.lang.Thread.run(Unknown Source)\
}

Comments
EVALUATION Closing as not a bug. Please reopen if it is reporducible with cache populated by anything else than 6u18b03.
19-11-2009

EVALUATION There was change in the cache format in the 6u18b03 (that is compatible with previous cache format). It was refined later for b04 and change in b04 is not compatible with b03. It is compatible with any other build though. I.e. a) cache created with 6u18b03 will trigger error with b04 b) cache created created with any other build should work with 6u18b04 without errors For a) error is expected. We chosed to not change cache format to avoif unneeded cache conversion for most of the users. Please clarify whether problem can be reporoduced with cache populated by anything else but 6u18b03.
06-11-2009