Connection timed out exception at second start

Hi all,

when I run a Java Web Start application, JWS downloads the application and starts it perfectly. When I run the application a second time, JWS searches for a new version and after a few minutes returns a "Connection timed out" exception:

JNLPException[category: Download-Fehler : Exception: java.net.ConnectException: Connection timed out: connect : LaunchDesc:null ]

at com.sun.javaws.cache.DownloadProtocol.doDownload(Unknown Source)

at com.sun.javaws.cache.DownloadProtocol.isLaunchFileUpdateAvailable(Unknown Source)

at com.sun.javaws.LaunchDownload.getUpdatedLaunchDesc(Unknown Source)

at com.sun.javaws.Launcher.downloadResources(Unknown Source)

at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)

at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)

at com.sun.javaws.Launcher.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

When I clear the JWS cache, the application is downloaded and started perfectly again.

Here is the JNLP file (abridged):

<?xml version="1.0" encoding="utf-8"?>

<jnlp spec="1.0+" codebase="..." href="...jnlp">

<information>

...

</information>

<security>

<all-permissions/>

</security>

<resources>

<j2se version="1.5 1.4 1.3" java-vm-args="-Xms32M -Xmx256M" />

<extension name="JavaHelp" href="../javahelp.jnlp" />

<extension name="..." href="....jnlp" />

<extension name="..." href="....jnlp" />

<extension name="..." href="....jnlp" />

<extension name="..." href="....jnlp" />

<jar href="....jar" />

</resources>

<application-desc main-class="...">

<argument>...</argument>

</application-desc>

</jnlp>

I know that other people don't have that problem, so I think it is a client problem, not a server problem.

Java Version is 1.5.0_10.

Any help?

Thanks in advance

Markus

[2620 byte] By [MaggusRa] at [2007-11-26 15:30:29]
# 1
No idea?
MaggusRa at 2007-7-8 21:47:08 > top of Java-index,Desktop,Deploying...
# 2

> No idea?

Only one. It is not so much an idea as a query,

and I cannot directly see how it would cause the

stated problem, but since you were polite enough

to wait three days, I will put forward my observations.

This line in your JNLP seemed odd to me.<j2se version="1.5 1.4 1.3" java-vm-args="-Xms32M -Xmx256M" />

My experience suggests that if you specify

"1.3+", and the user has 1.6, the application

is launched using 1.6. Is there any reason this

code will not run on Java 1.6 (or 1.7, or..)?

The second part of my query is..

Why are you attempting to grab extra memory

using the java-vm-args attribute?

The J2SE element offers initial-heap-size

& max-heap-size attributes. E.G.

Excerpt from..

http://www.physci.org/giffer/giffer0512.jnlp

<j2se

version="1.4.2+"

initial-heap-size="64m"

max-heap-size="512m" />

AndrewThompson64a at 2007-7-8 21:47:08 > top of Java-index,Desktop,Deploying...
# 3

Hi,

thanks for your answer.

I don't think it's a JNLP problem, because the first start of the program is no problem, just the second start results in the exception. And I know that other people don't have my problem.

But I changed the JNLP as recommended anyway, still the same problem (Java 6 is not supported by the program, 1.3 to 5 is).

Java Web Start is sending a "HTTP HEAD" instead of a "HTTP GET" at second start (to match timestamps?). May there a (client only) reason a HTTP GET is successfull where a HTTP HEAD is not?

Thanks in advance

Markus

MaggusRa at 2007-7-8 21:47:08 > top of Java-index,Desktop,Deploying...
# 4

Your reply convinces me that your problem is

beyond my expertise, sorry.

I am curious though, why code would work on

1.3, 1.4 & 1.5, but not 1.6?

(Do you mean, by your version list and

comments, that this code will not run

on 1.6?)

Message was edited by:

AndrewThompson64

AndrewThompson64a at 2007-7-8 21:47:08 > top of Java-index,Desktop,Deploying...