We use java Webstart to deploy a java application on our intranet. The application receives frequent updates. Once in awhile a user will launch the application from their de
Assuming the client JREs are up to date, you might try <update check="timeout" policy="always"/>
as suggested in this thread and described in the JNLP syntax documentation.
this problem is caused by offline-allowed
tag.
Per JNLP spec
If offline-allowed is specified, Java Web Start will also check to see if an update is available. However, if the application is already downloaded the check will timeout after a few seconds, in which case the cached application will be launched instead. Given a reasonably fast server connection, the latest version of the application will usually be run, but it is not guaranteed. The application, however, can be run offline.