JWS can't find the cache file for the application when trying to upgrade

Question

It happens since some of our users have updated their Java version to 1.6.0_01-b06 (all of us using W2K).
The first time they click on their usual desktop JWS shortcuts, all is working perfectly; the JWS 1.5 cache style shortcut is replaced by a new 1.6 cache style shortcut, the app is dowloaded again into its new cache location.
Troubles arise when the application is updated on the server side; the new jars are downloaded but the app, when launched via the shortcut, fails to start:
java.io.FileNotFoundException: c:\javaws\cache\6.0\10\4c37250a-47568a31 (Le fichier sp�cifi� est introuvable = File not found)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
at java.io.FileInputStream.<init>(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
This matches, as well as the title of this post (what a coincidence ...), the following bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6446676
which is declared to be "Closed and fixed", whereas it seems to be still alive. ..
It is a very annoying bug, because:
1) our client apps are able to work on Java 1.6 (although we still enforce the usage of a 1.5 jvm to run them), but as a workaround, due to this bug on the JWS part of 1.6, we have disabled all updates from JRE 1.5 to JRE 1.6.
2) it defeats one of the major strength of JWS we have "sold" to ours users: transparent and user friendly updates.
A final word: we deliver our Java apps using tomcat 5.5. Just to be sure we have experimented the same behavior using Apache.

Answer 1

Referenced as an open bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6549428