Java SE (Java Platform, Standard Edition)

It seems that Java 1.6 Web Start has a shorter 'check for update' timeout than with Java 1.5. My app is set up for offline allowed, and I have
<update check="timeout" policy="always"/>.
However, as noted by others, when javaws launches, with 1.6 it rarely downloads a new JNLP or jar file; instead, it runs with the cached version, and continues with the download in the background (whereas 1.5 would normally download it immediately). The next time the app is run, it will run with the newly cached files, so basically two app starts are needed to ensure that the latest files are used.

Is there any way to modify the timeout used here, from within the JNLP file (ie not a client configuration setting)? What would be ideal would be something like:
<update check="timeout" policy="always" timeout="5"/>
which might mean wait for 5 seconds before running with the cached copy.

thanks,
Stuart