Fail to update the jnlp file

The application allowed user to run offline. So ,I use <offline-allowed/> in the JNLP file.

It works well in JDK5.0:

1.the application can run if the network is dropped.

2.the jnlp file will be updated if the server update the JNLP.

But in when I change JDK to version 1.4.2, something unreasonable happened:

Even I update the server's JNLP, the client still use the old JNLP and not update it.

In the JWS1.4.2 Developer Guide, it says:"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."

What is the "a few seconds" mean?Is there any different between JDK1.4 and 1.5?

The connection between client and server is not very good. I do think it may cause the problem above. But in the same connection condition, JDK1.5 works..

So, is there any thing I can do to resolve this problem?

[1061 byte] By [Xingwanga] at [2007-11-26 13:53:19]
# 1
<jse version="1.5+" />(is one possibility)
AndrewThompson64a at 2007-7-8 1:31:23 > top of Java-index,Desktop,Deploying...
# 2
aha.. It's an idea but not a solution :)
Xingwanga at 2007-7-8 1:31:23 > top of Java-index,Desktop,Deploying...