About deployment.javaws.update.timeout = 0

Question

Hi,
I was very surprised to learn that setting :
deployment.javaws.update.timeout = 0
(see http://forum.java.sun.com/thread.jspa?threadID=661842&tstart=0)
meant an immediate start of jws without cache testing. I used to think that,traditionnallly in java, setting a 0 timeout meant that there was not timeout at all.
We achieved tests, changing our signed jar (the jnlp definition is also downloaded using a specific "Last-modified" HTTP header management via a proprietary servlet), and it appeared to successfuly download the new jar each time even on very low bandwidth environment.
This was not the case before setting deployment.javaws.update.timeout = 0 .
By the way knowing the information in the referenced thread makes me ask again for the basic question :
is there a mean to make the application starts exclusivly after the cache has been updated when necessary ? It is mandatory that our application must be updated for it can communicate with the server using our updated proprietary protocols. No work offline is possible.
This leads me to another question frequently asked (rarely solved) : is there a way to reduce the memory footprint of the jvm when it is started with jws ? Our tests proved that the memory consumed by the jvm launched using jws is far much bigger that when launched in the standard way .
Thanks in advance
//Marc

Answer 1

Disabling the computer's firewall and antivirus during the download and update usually resolves the error.