[GLASSFISH-20672] Deploying new version of ear with components with new version numbers caches javaws to break due to caching in java 7 update 21 Created: 28/Jun/13 Updated: 28/Jun/13
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Tags:||app-client, appclient, cache, java, java7, java_7, java_web_start|
When we switched to Java 7 update 21 from Java 7 update 17 we noticed that the apps that we run with Java Web Start started to fail to start after a new deployment of the same app with a different version number.
It seems the auto-generated jnlp files are referencing a full path to the component (including the version) and when it gets a 404 (because the file can now be found under the very similar url with just the build number different).
It seems this could be a bug with Java 7 update 21 or an issue with what files are being cached because of the Java Web Start on glassfish 126.96.36.199.
I could not find any bug for Java or glassfish for this.
Run the JavaWS app
Then make a new build and deploy
And we get a file not found for something like:
Please let me know if you need any more information.